Abyss-lord commented on PR #6497: URL: https://github.com/apache/gravitino/pull/6497#issuecomment-2680117726
> > > Even if we have a use case for this, we'll need a design for the output. For example, should we always quote a field value with `""`? What if there are `,` in a field value that breaks the parser? How do we want a boolean value to be presented? `true` or `"true"` or `TRUE` or something else? How will we present null values? so on and so forth. > > > We NEVER do something simply because it is DOABLE. There are simply a thousand ways to spend your precious time. > > > > > > @tengqm The main thing is that we can't use web UI on our side, and users are not professional and technical personnel. There is no need to use Java API or REST API to create and delete tables for now. We need to provide a simple and practical client-side script for non-technical people to query(just list\ details). > > Okay, we can support tabular output for command line users, where the most important fields are included. For cases where there are too many fields, we can simply dump the JSON response. So ... I don't see a need for CSV output. Am I missing something? @tengqm @justinmclean Yes, just to be consistent with the tableformat output logic, Whether the plainformat and tableformat outputs are inconsistent for the same entity -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@gravitino.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
