[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[ https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14980596#comment-14980596 ] Alan Gates commented on HIVE-11564: --- I linked it to HIVE-9752, which is already labeled TODO2.0 so that should be good. > HBaseSchemaTool should be able to list objects > -- > > Key: HIVE-11564 > URL: https://issues.apache.org/jira/browse/HIVE-11564 > Project: Hive > Issue Type: Improvement > Components: HBase Metastore >Affects Versions: 2.0.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 2.0.0 > > Attachments: HIVE-11564.2.patch, HIVE-11564.3.patch, > HIVE-11564.4.patch, HIVE-11564.5.patch, HIVE-11564.patch > > > Current HBaseSchemaTool can only fetch objects the user already knows the > name of. It should also be able to list available objects (e.g. list all > databases). > It is also very user unfriendly in terms of error handling. That needs to be > fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[
https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14978636#comment-14978636
]
Hive QA commented on HIVE-11564:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12769071/HIVE-11564.5.patch
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 9730 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.hwi.TestHWISessionManager.testHiveDriver
org.apache.hive.jdbc.TestSSL.testSSLVersion
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5828/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5828/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5828/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12769071 - PreCommit-HIVE-TRUNK-Build
> HBaseSchemaTool should be able to list objects
> --
>
> Key: HIVE-11564
> URL: https://issues.apache.org/jira/browse/HIVE-11564
> Project: Hive
> Issue Type: Improvement
> Components: HBase Metastore
>Affects Versions: 2.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
> Fix For: 2.0.0
>
> Attachments: HIVE-11564.2.patch, HIVE-11564.3.patch,
> HIVE-11564.4.patch, HIVE-11564.5.patch, HIVE-11564.patch
>
>
> Current HBaseSchemaTool can only fetch objects the user already knows the
> name of. It should also be able to list available objects (e.g. list all
> databases).
> It is also very user unfriendly in terms of error handling. That needs to be
> fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[ https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979841#comment-14979841 ] Lefty Leverenz commented on HIVE-11564: --- This needs doc, right? We can give it a TODOC2.0 label, but it should also be linked to HIVE-9752 (Documentation for HBase metastore) just to keep track of everything in one place. Or maybe HIVE-9752 is sufficient and this issue doesn't need its own TODOC2.0 label. What do you think, [~alangates]? > HBaseSchemaTool should be able to list objects > -- > > Key: HIVE-11564 > URL: https://issues.apache.org/jira/browse/HIVE-11564 > Project: Hive > Issue Type: Improvement > Components: HBase Metastore >Affects Versions: 2.0.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 2.0.0 > > Attachments: HIVE-11564.2.patch, HIVE-11564.3.patch, > HIVE-11564.4.patch, HIVE-11564.5.patch, HIVE-11564.patch > > > Current HBaseSchemaTool can only fetch objects the user already knows the > name of. It should also be able to list available objects (e.g. list all > databases). > It is also very user unfriendly in terms of error handling. That needs to be > fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[ https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975817#comment-14975817 ] Daniel Dai commented on HIVE-11564: --- Another issue two issues: 1. After "HBaseSchemaTool().install", we shall exit schematools rather than continue 2. list-tables should not has args > HBaseSchemaTool should be able to list objects > -- > > Key: HIVE-11564 > URL: https://issues.apache.org/jira/browse/HIVE-11564 > Project: Hive > Issue Type: Improvement > Components: HBase Metastore >Affects Versions: 2.0.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 2.0.0 > > Attachments: HIVE-11564.2.patch, HIVE-11564.3.patch, > HIVE-11564.4.patch, HIVE-11564.patch > > > Current HBaseSchemaTool can only fetch objects the user already knows the > name of. It should also be able to list available objects (e.g. list all > databases). > It is also very user unfriendly in terms of error handling. That needs to be > fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[ https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976948#comment-14976948 ] Daniel Dai commented on HIVE-11564: --- +1 > HBaseSchemaTool should be able to list objects > -- > > Key: HIVE-11564 > URL: https://issues.apache.org/jira/browse/HIVE-11564 > Project: Hive > Issue Type: Improvement > Components: HBase Metastore >Affects Versions: 2.0.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 2.0.0 > > Attachments: HIVE-11564.2.patch, HIVE-11564.3.patch, > HIVE-11564.4.patch, HIVE-11564.5.patch, HIVE-11564.patch > > > Current HBaseSchemaTool can only fetch objects the user already knows the > name of. It should also be able to list available objects (e.g. list all > databases). > It is also very user unfriendly in terms of error handling. That needs to be > fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[ https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14974875#comment-14974875 ] Daniel Dai commented on HIVE-11564: --- Some initial comments: 1. Where is the "install" cmd after the patch? 2. Why "table" option is required? Can we only do "list-tables"? 3. In case command line parsing exception, can we print out the exception in addition to print the usage? > HBaseSchemaTool should be able to list objects > -- > > Key: HIVE-11564 > URL: https://issues.apache.org/jira/browse/HIVE-11564 > Project: Hive > Issue Type: Improvement > Components: HBase Metastore >Affects Versions: 2.0.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 2.0.0 > > Attachments: HIVE-11564.2.patch, HIVE-11564.3.patch, HIVE-11564.patch > > > Current HBaseSchemaTool can only fetch objects the user already knows the > name of. It should also be able to list available objects (e.g. list all > databases). > It is also very user unfriendly in terms of error handling. That needs to be > fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[ https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975230#comment-14975230 ] Alan Gates commented on HIVE-11564: --- bq. Where is the "install" cmd after the patch? oops. Good catch. I'll put that back. bq. Why "table" option is required? Can we only do "list-tables"? Yep, I'll remove that required, as it doesn't make sense for list-tables or install. bq. In case command line parsing exception, can we print out the exception in addition to print the usage? Makes sense, will do. > HBaseSchemaTool should be able to list objects > -- > > Key: HIVE-11564 > URL: https://issues.apache.org/jira/browse/HIVE-11564 > Project: Hive > Issue Type: Improvement > Components: HBase Metastore >Affects Versions: 2.0.0 >Reporter: Alan Gates >Assignee: Alan Gates > Fix For: 2.0.0 > > Attachments: HIVE-11564.2.patch, HIVE-11564.3.patch, HIVE-11564.patch > > > Current HBaseSchemaTool can only fetch objects the user already knows the > name of. It should also be able to list available objects (e.g. list all > databases). > It is also very user unfriendly in terms of error handling. That needs to be > fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[
https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14970873#comment-14970873
]
Hive QA commented on HIVE-11564:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12768075/HIVE-11564.3.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 9719 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.ql.io.orc.TestColumnStatistics.testHasNull
org.apache.hadoop.hive.ql.io.orc.TestJsonFileDump.testJsonDump
org.apache.hive.hcatalog.api.TestHCatClient.testTableSchemaPropagation
org.apache.hive.jdbc.TestSSL.testSSLVersion
{noformat}
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5748/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5748/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5748/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 4 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12768075 - PreCommit-HIVE-TRUNK-Build
> HBaseSchemaTool should be able to list objects
> --
>
> Key: HIVE-11564
> URL: https://issues.apache.org/jira/browse/HIVE-11564
> Project: Hive
> Issue Type: Improvement
> Components: HBase Metastore
>Affects Versions: 2.0.0
>Reporter: Alan Gates
>Assignee: Alan Gates
> Fix For: 2.0.0
>
> Attachments: HIVE-11564.2.patch, HIVE-11564.3.patch, HIVE-11564.patch
>
>
> Current HBaseSchemaTool can only fetch objects the user already knows the
> name of. It should also be able to list available objects (e.g. list all
> databases).
> It is also very user unfriendly in terms of error handling. That needs to be
> fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[
https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725229#comment-14725229
]
Hive QA commented on HIVE-11564:
{color:red}Overall{color}: -1 no tests executed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12753370/HIVE-11564.2.patch
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5132/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5132/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5132/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hive-ptest/working/scratch/source-prep.sh' failed with exit
status 1 and output '+ [[ -n /usr/java/jdk1.7.0_45-cloudera ]]
+ export JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ export
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.7.0_45-cloudera/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.7.0_45-cloudera/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'M2_OPTS=-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost
-Dhttp.proxyPort=3128'
+ M2_OPTS='-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost
-Dhttp.proxyPort=3128'
+ cd /data/hive-ptest/working/
+ tee /data/hive-ptest/logs/PreCommit-HIVE-TRUNK-Build-5132/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ git = \s\v\n ]]
+ [[ git = \g\i\t ]]
+ [[ -z master ]]
+ [[ -d apache-github-source-source ]]
+ [[ ! -d apache-github-source-source/.git ]]
+ [[ ! -d apache-github-source-source ]]
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at 8f930e5 HIVE-11504: Predicate pushing down doesn't work for
float type for Parquet(Ferdinand Xu, reviewed by Sergio Pena and Owen O'Malley)
+ git clean -f -d
Removing
itests/hive-minikdc/src/test/java/org/apache/hive/minikdc/TestJdbWithCustomAuthWithKerberos.java
Removing
shims/common/src/main/java/org/apache/hadoop/hive/thrift/DefaultKrbCustomAuthenticationProviderImpl.java
Removing
shims/common/src/main/java/org/apache/hadoop/hive/thrift/KrbCustomAuthenticationProvider.java
+ git checkout master
Already on 'master'
+ git reset --hard origin/master
HEAD is now at 8f930e5 HIVE-11504: Predicate pushing down doesn't work for
float type for Parquet(Ferdinand Xu, reviewed by Sergio Pena and Owen O'Malley)
+ git merge --ff-only origin/master
Already up-to-date.
+ git gc
+ patchCommandPath=/data/hive-ptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hive-ptest/working/scratch/build.patch
+ [[ -f /data/hive-ptest/working/scratch/build.patch ]]
+ chmod +x /data/hive-ptest/working/scratch/smart-apply-patch.sh
+ /data/hive-ptest/working/scratch/smart-apply-patch.sh
/data/hive-ptest/working/scratch/build.patch
The patch does not appear to apply with p0, p1, or p2
+ exit 1
'
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12753370 - PreCommit-HIVE-TRUNK-Build
> HBaseSchemaTool should be able to list objects
> --
>
> Key: HIVE-11564
> URL: https://issues.apache.org/jira/browse/HIVE-11564
> Project: Hive
> Issue Type: Improvement
> Components: HBase Metastore
>Affects Versions: hbase-metastore-branch
>Reporter: Alan Gates
>Assignee: Alan Gates
> Attachments: HIVE-11564.2.patch, HIVE-11564.patch
>
>
> Current HBaseSchemaTool can only fetch objects the user already knows the
> name of. It should also be able to list available objects (e.g. list all
> databases).
> It is also very user unfriendly in terms of error handling. That needs to be
> fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[ https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724149#comment-14724149 ] Daniel Dai commented on HIVE-11564: --- Not sure if we can provide partial types to BinarySortableSerDe to extract only dbName/tblName from partition key. But if this has been tested, then it should be fine. > HBaseSchemaTool should be able to list objects > -- > > Key: HIVE-11564 > URL: https://issues.apache.org/jira/browse/HIVE-11564 > Project: Hive > Issue Type: Improvement > Components: HBase Metastore >Affects Versions: hbase-metastore-branch >Reporter: Alan Gates >Assignee: Alan Gates > Attachments: HIVE-11564.2.patch, HIVE-11564.patch > > > Current HBaseSchemaTool can only fetch objects the user already knows the > name of. It should also be able to list available objects (e.g. list all > databases). > It is also very user unfriendly in terms of error handling. That needs to be > fixed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HIVE-11564) HBaseSchemaTool should be able to list objects
[
https://issues.apache.org/jira/browse/HIVE-11564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14707931#comment-14707931
]
Hive QA commented on HIVE-11564:
{color:red}Overall{color}: -1 no tests executed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12751848/HIVE-11564.patch
Test results:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5043/testReport
Console output:
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/5043/console
Test logs:
http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-5043/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Tests exited with: NonZeroExitCodeException
Command 'bash /data/hive-ptest/working/scratch/source-prep.sh' failed with exit
status 1 and output '+ [[ -n /usr/java/jdk1.7.0_45-cloudera ]]
+ export JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ JAVA_HOME=/usr/java/jdk1.7.0_45-cloudera
+ export
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.7.0_45-cloudera/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+
PATH=/usr/java/jdk1.7.0_45-cloudera/bin/:/usr/local/apache-maven-3.0.5/bin:/usr/java/jdk1.7.0_45-cloudera/bin:/usr/local/apache-ant-1.9.1/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/hiveptest/bin
+ export 'ANT_OPTS=-Xmx1g -XX:MaxPermSize=256m '
+ ANT_OPTS='-Xmx1g -XX:MaxPermSize=256m '
+ export 'M2_OPTS=-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost
-Dhttp.proxyPort=3128'
+ M2_OPTS='-Xmx1g -XX:MaxPermSize=256m -Dhttp.proxyHost=localhost
-Dhttp.proxyPort=3128'
+ cd /data/hive-ptest/working/
+ tee /data/hive-ptest/logs/PreCommit-HIVE-TRUNK-Build-5043/source-prep.txt
+ [[ false == \t\r\u\e ]]
+ mkdir -p maven ivy
+ [[ git = \s\v\n ]]
+ [[ git = \g\i\t ]]
+ [[ -z master ]]
+ [[ -d apache-github-source-source ]]
+ [[ ! -d apache-github-source-source/.git ]]
+ [[ ! -d apache-github-source-source ]]
+ cd apache-github-source-source
+ git fetch origin
+ git reset --hard HEAD
HEAD is now at 3c1eae0 HIVE-11596: nvl(x, y) throws NPE if type x and type y
doesn't match, rather than throwing the meaningful error (Aihua Xu, reviewed by
Chao Sun)
+ git clean -f -d
Removing common/src/java/org/apache/hadoop/hive/conf/HiveConf.java.orig
+ git checkout master
Already on 'master'
+ git reset --hard origin/master
HEAD is now at 3c1eae0 HIVE-11596: nvl(x, y) throws NPE if type x and type y
doesn't match, rather than throwing the meaningful error (Aihua Xu, reviewed by
Chao Sun)
+ git merge --ff-only origin/master
Already up-to-date.
+ git gc
+ patchCommandPath=/data/hive-ptest/working/scratch/smart-apply-patch.sh
+ patchFilePath=/data/hive-ptest/working/scratch/build.patch
+ [[ -f /data/hive-ptest/working/scratch/build.patch ]]
+ chmod +x /data/hive-ptest/working/scratch/smart-apply-patch.sh
+ /data/hive-ptest/working/scratch/smart-apply-patch.sh
/data/hive-ptest/working/scratch/build.patch
The patch does not appear to apply with p0, p1, or p2
+ exit 1
'
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12751848 - PreCommit-HIVE-TRUNK-Build
HBaseSchemaTool should be able to list objects
--
Key: HIVE-11564
URL: https://issues.apache.org/jira/browse/HIVE-11564
Project: Hive
Issue Type: Improvement
Components: HBase Metastore
Affects Versions: hbase-metastore-branch
Reporter: Alan Gates
Assignee: Alan Gates
Attachments: HIVE-11564.patch
Current HBaseSchemaTool can only fetch objects the user already knows the
name of. It should also be able to list available objects (e.g. list all
databases).
It is also very user unfriendly in terms of error handling. That needs to be
fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
