[
https://issues.apache.org/jira/browse/HDFS-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Liang updated HDFS-12321:
------------------------------
Attachment: HDFS-12321-HDFS-7240.008.patch
[~anu] submit v008 patch based on your v007 patch. Now it works like:
in json we specify something like:
{{listSkipping}}
{{select * from volumeInfo where volumeName like :A: and userName != :B:;}}
and CLI recognize it as having two arguments, A at position#1, and B at
position#2.
then from command one can do:
{{hdfs ozsqlquery --listSkipping B=userName A=volume123 -o out -p in.db}}
then the parser takes an argument list of B=userName A=volume123 (yes, A and B
can be out of order). And map it as position A = position#1 = volume123, B =
position#2 = userName, and insert into the SQL query.
> Ozone : debug cli: add support to load user-provided SQL query
> --------------------------------------------------------------
>
> Key: HDFS-12321
> URL: https://issues.apache.org/jira/browse/HDFS-12321
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chen Liang
> Assignee: Chen Liang
> Fix For: ozone
>
> Attachments: HDFS-12321-HDFS-7240.001.patch,
> HDFS-12321-HDFS-7240.002.patch, HDFS-12321-HDFS-7240.003.patch,
> HDFS-12321-HDFS-7240.004.patch, HDFS-12321-HDFS-7240.005.patch,
> HDFS-12321-HDFS-7240.006.patch, HDFS-12321-HDFS-7240.007.patch,
> HDFS-12321-HDFS-7240.008.patch
>
>
> This JIRA extends SQL CLI to support loading a user-provided file that
> includes any sql query the user wants to run on the SQLite db obtained by
> converting Ozone metadata db.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
