[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422908#comment-16422908
]
Vaibhav Gumashta commented on HIVE-18963:
-
[~thejas] I ran the test locally and it passes. The TestJdbcWithMiniHA fails
because the MiniHS2 port is still in use (the test perhaps needs some cleanup).
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
> Attachments: HIVE-18963.1.patch, HIVE-18963.2.patch,
> HIVE-18963.3.patch
>
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422707#comment-16422707
]
Thejas M Nair commented on HIVE-18963:
--
[~vgumashta]
Two other failures are in jdbc/beeline (with test age=1), can you please check
if they could be related ?
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
> Attachments: HIVE-18963.1.patch, HIVE-18963.2.patch,
> HIVE-18963.3.patch
>
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422705#comment-16422705
]
Thejas M Nair commented on HIVE-18963:
--
https://builds.apache.org/job/PreCommit-HIVE-Build/9956/testReport/org.apache.hadoop.hive.ql.processors/TestCommandProcessorFactory/testAvailableCommands/
test failure seems to be related to another patch - HIVE-19033
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
> Attachments: HIVE-18963.1.patch, HIVE-18963.2.patch,
> HIVE-18963.3.patch
>
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422024#comment-16422024
]
Hive QA commented on HIVE-18963:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12917162/HIVE-18963.3.patch
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 192 failed/errored test(s), 13297 tests
executed
*Failed tests:*
{noformat}
TestCopyUtils - did not produce a TEST-*.xml file (likely timed out)
(batchId=230)
TestDbNotificationListener - did not produce a TEST-*.xml file (likely timed
out) (batchId=246)
TestExportImport - did not produce a TEST-*.xml file (likely timed out)
(batchId=230)
TestHCatHiveCompatibility - did not produce a TEST-*.xml file (likely timed
out) (batchId=246)
TestNegativeCliDriver - did not produce a TEST-*.xml file (likely timed out)
(batchId=95)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422001#comment-16422001
]
Hive QA commented on HIVE-18963:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
47s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
24s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
42s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
53s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
9s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:red}-1{color} | {color:red} mvninstall {color} | {color:red} 0m
21s{color} | {color:red} beeline in the patch failed. {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
31s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
14s{color} | {color:red} beeline: The patch generated 11 new + 79 unchanged - 5
fixed = 90 total (was 84) {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
13s{color} | {color:red} jdbc: The patch generated 2 new + 13 unchanged - 8
fixed = 15 total (was 21) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
13s{color} | {color:red} beeline generated 1 new + 2 unchanged - 0 fixed = 3
total (was 2) {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m
14s{color} | {color:red} jdbc generated 2 new + 1 unchanged - 0 fixed = 3 total
(was 1) {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m
16s{color} | {color:red} The patch generated 49 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 17m 18s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense javac javadoc findbugs checkstyle compile
xml |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9956/dev-support/hive-personality.sh
|
| git revision | master / 13f59a2 |
| Default Java | 1.8.0_111 |
| mvninstall |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9956/yetus/patch-mvninstall-beeline.txt
|
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9956/yetus/diff-checkstyle-beeline.txt
|
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9956/yetus/diff-checkstyle-jdbc.txt
|
| javadoc |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9956/yetus/diff-javadoc-javadoc-beeline.txt
|
| javadoc |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9956/yetus/diff-javadoc-javadoc-jdbc.txt
|
| asflicense |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9956/yetus/patch-asflicense-problems.txt
|
| modules | C: beeline itests/hive-unit jdbc U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9956/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
>
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16421953#comment-16421953
]
Thejas M Nair commented on HIVE-18963:
--
+1 pending tests
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
> Attachments: HIVE-18963.1.patch, HIVE-18963.2.patch,
> HIVE-18963.3.patch
>
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405955#comment-16405955
]
Hive QA commented on HIVE-18963:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12915264/HIVE-18963.1.patch
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 123 failed/errored test(s), 13797 tests
executed
*Failed tests:*
{noformat}
TestMiniLlapCliDriver - did not produce a TEST-*.xml file (likely timed out)
(batchId=150)
[intersect_all.q,unionDistinct_1.q,orc_ppd_schema_evol_3a.q,table_nonprintable.q,tez_union_dynamic_partition.q,tez_union_dynamic_partition_2.q,mm_cttas.q,global_limit.q,schemeAuthority.q,cte_2.q,rcfile_createas1.q,dynamic_partition_pruning_2.q,intersect_merge.q,parallel_colstats.q,load_hdfs_file_with_space_in_the_name.q]
TestMinimrCliDriver - did not produce a TEST-*.xml file (likely timed out)
(batchId=92)
[infer_bucket_sort_num_buckets.q,infer_bucket_sort_reducers_power_two.q,parallel_orderby.q,bucket_num_reducers_acid.q,infer_bucket_sort_map_operators.q,infer_bucket_sort_merge.q,root_dir_external_table.q,infer_bucket_sort_dyn_part.q,udf_using.q,bucket_num_reducers_acid2.q]
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[acid_table_stats]
(batchId=54)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[auto_sortmerge_join_2]
(batchId=49)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[ppd_join5] (batchId=36)
org.apache.hadoop.hive.cli.TestMiniDruidCliDriver.testCliDriver[druidmini_mv]
(batchId=251)
org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[llap_smb]
(batchId=152)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[bucket_map_join_tez_empty]
(batchId=158)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[default_constraint]
(batchId=162)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[groupby_groupingset_bug]
(batchId=172)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[insert_values_orig_table_use_metadata]
(batchId=168)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[mergejoin]
(batchId=167)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[results_cache_1]
(batchId=168)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[sysdb]
(batchId=161)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[tez_smb_main]
(batchId=159)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[update_access_time_non_current_db]
(batchId=170)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vectorization_div0]
(batchId=169)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vectorized_dynamic_semijoin_reduction]
(batchId=153)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.org.apache.hadoop.hive.cli.TestNegativeCliDriver
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[mm_convert]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[mm_truncate_cols]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[smb_bucketmapjoin]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[smb_mapjoin_14]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[sortmerge_mapjoin_mismatch_1]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[split_sample_out_of_range]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[split_sample_wrong_format]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[stats_aggregator_error_1]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[stats_aggregator_error_2]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[stats_publisher_error_1]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[strict_join_2]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[strict_orderby]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[strict_orderby_2]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[strict_pruning_2]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_corr_grandparent]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_corr_in_agg]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_in_groupby]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_multiple_cols_in_select]
(batchId=95)
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_notin_implicit_gby]
(batchId=95)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405912#comment-16405912
]
Hive QA commented on HIVE-18963:
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
1s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
34s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
8s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
50s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
23s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
30s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
7s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 0m
10s{color} | {color:red} beeline: The patch generated 5 new + 80 unchanged - 3
fixed = 85 total (was 83) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
31s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} asflicense {color} | {color:red} 0m
12s{color} | {color:red} The patch generated 49 ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 11m 43s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense javac javadoc findbugs checkstyle compile
xml |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-9717/dev-support/hive-personality.sh
|
| git revision | master / 68459cf |
| Default Java | 1.8.0_111 |
| checkstyle |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9717/yetus/diff-checkstyle-beeline.txt
|
| asflicense |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9717/yetus/patch-asflicense-problems.txt
|
| modules | C: beeline itests/hive-unit U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-9717/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
> Attachments: HIVE-18963.1.patch
>
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16405863#comment-16405863
]
Vaibhav Gumashta commented on HIVE-18963:
-
[~vihangk1] I'm attaching a patch which has a test case which details what I
was thinking of adding. Let me know what you think. Thanks!
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
> Attachments: HIVE-18963.1.patch
>
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401462#comment-16401462
]
Vihang Karajgaonkar commented on HIVE-18963:
{quote}I think we should have a way to specify the final jdbc url (including
not just the host:port, but other connection/session/conf params). That would
be a nice usability add on - what do you think?
{quote}
It does support connection params in the url using the xml file. Check
[this|https://github.com/apache/hive/blob/master/beeline/src/test/org/apache/hive/beeline/hs2connection/TestUserHS2ConnectionFileParser.java#L101]
test case for example. This test also has other examples of urls which can be
supported using the xml file. Is this not want you are looking for here?
{quote}We should also have a way to specify urls (let's call it named urls) for
different HS2 services. For example, let's say there are 2 different versions
of the service running on the cluster, the user can connect to a specific
instance like this: {{beeline -c namedUrl}}. We can keep a default url as well
which gets picked if no namedUrl switch is provided on command line.
{quote}
This would be a good improvement. I myself had this at the back of my mind but
I never got around working on it. I think it would be a good addition.
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401320#comment-16401320
]
Vaibhav Gumashta commented on HIVE-18963:
-
[~vihangk1] Looked at the patch and a couple things that would be nice to have
in addition to what the patch adds:
1. I think we should have a way to specify the final jdbc url (including not
just the host:port, but other connection/session/conf params). That would be a
nice usability add on - what do you think?
2. We should also have a way to specify urls (let's call it named urls) for
different HS2 services. For example, let's say there are 2 different versions
of the service running on the cluster, the user can connect to a specific
instance like this: {{beeline -c namedUrl}}. We can keep a default url as well
which gets picked if no namedUrl switch is provided on command line.
Let me know what you think about these additions - I can create a patch with
these changes. Thanks!
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400753#comment-16400753
]
Vihang Karajgaonkar commented on HIVE-18963:
Thanks [~vgumashta]. Let me know if you need any help from my side. I would be
happy to help.
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16400740#comment-16400740
]
Vaibhav Gumashta commented on HIVE-18963:
-
[~vihangk1] Thanks for pointing me to HIVE-14063. Let me take a look at that
patch and see if it serves this use case.
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16399860#comment-16399860
]
Vihang Karajgaonkar commented on HIVE-18963:
beeline-site.xml sounds so much better than beeline-hs2-connection.xml. I
wonder why I didn't think of that name in HIVE-14063 :(
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-18963) JDBC: Provide an option to simplify beeline usage by supporting default and named URL for beeline
[
https://issues.apache.org/jira/browse/HIVE-18963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16399859#comment-16399859
]
Vihang Karajgaonkar commented on HIVE-18963:
Thanks [~vgumashta] for creating this. I think it would be a very useful
feature. How does this request relate to HIVE-14063? That patch used
hive-site.xml and beeline-hs2-connection.xml files to automatically connect to
the HS2. I am not aware of beeline-site.xml. Is this patch planning to
introduce a new file called beeline-site.xml or it already exists? Can we reuse
some of the work done for HIVE-14063? Thanks!
> JDBC: Provide an option to simplify beeline usage by supporting default and
> named URL for beeline
> -
>
> Key: HIVE-18963
> URL: https://issues.apache.org/jira/browse/HIVE-18963
> Project: Hive
> Issue Type: Bug
> Components: Beeline
>Reporter: Vaibhav Gumashta
>Assignee: Vaibhav Gumashta
>Priority: Major
>
> Currently, after opening Beeline CLI, the user needs to supply a connection
> string to use the HS2 instance and set up the jdbc driver. Since we plan to
> replace Hive CLI with Beeline in future (HIVE-10511), it will help the
> usability if the user can simply type {{beeline}} and get start the hive
> session. The jdbc url can be specified in a beeline-site.xml (which can
> contain other named jdbc urls as well, and they can be accessed by something
> like: {{beeline -c namedUrl}}. The use of beeline-site.xml can also be
> potentially expanded later if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
