doc/radosgw: Redd up s3select.rst as followup to #49411#50384
doc/radosgw: Redd up s3select.rst as followup to #49411#50384
Conversation
| | on each run with a different dataset(random). | ||
| | (2) Compares results of queries whose syntax is different but which are semantically equivalent. | ||
| | This kind of test validates that different runtime flows produce an identical result | ||
| | on each run with a different, random dataset. |
doc/radosgw/s3select.rst
Outdated
| | These objects and arrays can be nested within each other without any limitations. | ||
| | upon using SQL to query a specific value in a JSON document, the user needs to use a specific syntax to describe the location of the value. | ||
| | When using SQL to query a specific value in a JSON document, the user needs to use a specific syntax to describe the location of the value. | ||
| | This is because the standard "select column from object" syntax will not work. |
There was a problem hiding this comment.
this line(556) may removed.
doc/radosgw/s3select.rst
Outdated
| | upon using SQL to query a specific value in a JSON document, the user needs to use a specific syntax to describe the location of the value. | ||
| | When using SQL to query a specific value in a JSON document, the user needs to use a specific syntax to describe the location of the value. | ||
| | This is because the standard "select column from object" syntax will not work. | ||
| | Instead, the user must use a path in the SELECT statement to tell the JSON reader where the value is located. |
There was a problem hiding this comment.
and use the following:
The user must use a path in the SELECT statement to tell the JSON reader where the value is located.
There was a problem hiding this comment.
I've recast this in a slightly different way, PTAL. I was hesitant to do too much restructuring since my SQL-fu is weak.
There was a problem hiding this comment.
Thanks for reviewing and editing.
there is much SQL examples for the use case of JSON, in this document and also in the Repo itself.
i hope it is enough.
768230c to
b1be592
Compare
| | This is because the standard "select column from object" syntax will not work. | ||
| | Instead, the user must use a path in the SELECT statement to tell the JSON reader where the value is located. | ||
| | When using SQL to query a specific value in a JSON document, the client must specify the location of the value | ||
| | via a path in the SELECT statement. |
doc/radosgw/s3select.rst
Outdated
| | - escape character disables any special characters, except for row delimiter. | ||
| | The ``s3-select`` engine contains a CSV parser, which parses s3-objects as follows. | ||
| | - Each row ends with ``row-delimiter``. | ||
| | - ``field-separator`` separates adjacent columns, successive ``field separator``s define a NULL column. |
There was a problem hiding this comment.
@anthonyeleven: I suspect that the s after field separator has to be escaped, but I haven't tested it locally, so this is just a self-educated guess. So:
s|field separator| field separator `` \s|
I suspect.
There was a problem hiding this comment.
I rephrase to avoid the uncertainty, ptal
There was a problem hiding this comment.
That did it. It got past the checks.
I'm going to merge this and create backports.
Signed-off-by: Anthony D'Atri <anthonyeleven@users.noreply.github.com>
b1be592 to
78b42ee
Compare
doc/radosgw: Redd up s3select.rst as followup to #49411
Caps, whitespace, wording, formatting, all the usual OCD.
Signed-off-by: Anthony D'Atri anthonyeleven@users.noreply.github.com
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windows