[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446560#comment-16446560 ] Eugene Koifman commented on HIVE-19260: --- [~prasanth_j] could you review please > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446565#comment-16446565 ] Prasanth Jayachandran commented on HIVE-19260: -- In findRelatedLocks() partition name is missing equalsIgnoreCase(). LockComparator missing null check for dbName. > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446570#comment-16446570 ] Eugene Koifman commented on HIVE-19260: --- partition column names are never specified by caller - they are taken from table metdata which is normalize and I don't think lower casing partition values is a good idea. I don't see any LockComparator changes here. in fact, findRelatedLocks() is not even necessary given the other changes - being a bit paranoid here. > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447171#comment-16447171 ] Hive QA commented on HIVE-19260: | (/) *{color:green}+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 52s{color} | {color:blue} Maven dependency ordering for branch {color} | | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m 5s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 46s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m 36s{color} | {color:green} master passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 31s{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:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m 11s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m 40s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m 40s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m 34s{color} | {color:green} the patch passed {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} javadoc {color} | {color:green} 2m 34s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 15s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 25m 49s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Optional Tests | asflicense javac javadoc findbugs checkstyle compile | | 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-10403/dev-support/hive-personality.sh | | git revision | master / 84481cf | | Default Java | 1.8.0_111 | | modules | C: hcatalog/streaming ql standalone-metastore streaming U: . | | Console output | http://104.198.109.242/logs//PreCommit-HIVE-Build-10403/yetus.txt | | Powered by | Apache Yetushttp://yetus.apache.org | This message was automatically generated. > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447182#comment-16447182 ] Hive QA commented on HIVE-19260: Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12920123/HIVE-19260.01.patch {color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified. {color:red}ERROR:{color} -1 due to 24 failed/errored test(s), 14284 tests executed *Failed tests:* {noformat} TestMinimrCliDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=93) [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] TestNonCatCallsWithCatalog - did not produce a TEST-*.xml file (likely timed out) (batchId=217) org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[parquet_vectorization_0] (batchId=17) org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[results_cache_invalidation2] (batchId=39) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[check_constraint] (batchId=158) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[default_constraint] (batchId=163) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[results_cache_invalidation2] (batchId=163) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[sysdb] (batchId=163) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[tez_smb_1] (batchId=171) org.apache.hadoop.hive.cli.TestMiniSparkOnYarnCliDriver.testCliDriver[bucketizedhiveinputformat] (batchId=183) org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_5] (batchId=105) org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[cluster_tasklog_retrieval] (batchId=98) org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[mapreduce_stack_trace] (batchId=98) org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[mapreduce_stack_trace_turnoff] (batchId=98) org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[minimr_broken_pipe] (batchId=98) org.apache.hadoop.hive.ql.TestAcidOnTez.testAcidInsertWithRemoveUnion (batchId=228) org.apache.hadoop.hive.ql.TestAcidOnTez.testCtasTezUnion (batchId=228) org.apache.hadoop.hive.ql.TestAcidOnTez.testNonStandardConversion01 (batchId=228) org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1 (batchId=232) org.apache.hadoop.hive.ql.lockmgr.TestDbTxnManager2.testWriteSetTracking3 (batchId=300) org.apache.hive.beeline.TestBeeLineWithArgs.testQueryProgress (batchId=235) org.apache.hive.beeline.TestBeeLineWithArgs.testQueryProgressParallel (batchId=235) org.apache.hive.jdbc.TestTriggersMoveWorkloadManager.testTriggerMoveAndKill (batchId=242) org.apache.hive.minikdc.TestJdbcWithMiniKdcCookie.testCookieNegative (batchId=254) {noformat} Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/10403/testReport Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/10403/console Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-10403/ Messages: {noformat} Executing org.apache.hive.ptest.execution.TestCheckPhase Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.YetusPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Executing org.apache.hive.ptest.execution.ReportingPhase Tests exited with: TestsFailedException: 24 tests failed {noformat} This message is automatically generated. ATTACHMENT ID: 12920123 - PreCommit-HIVE-Build > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447544#comment-16447544 ] Prasanth Jayachandran commented on HIVE-19260: -- is o1.getDbname() guaranteed to be non-null in LockComparator? > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450170#comment-16450170 ] Eugene Koifman commented on HIVE-19260: --- yes, it guaranteed to be not null > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450265#comment-16450265 ] Prasanth Jayachandran commented on HIVE-19260: -- ok. lgtm, +1 > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01-branch-3.patch, HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450362#comment-16450362 ] Eugene Koifman commented on HIVE-19260: --- Thanks Prasanth for the review committed to master > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01-branch-3.patch, HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452198#comment-16452198 ] Hive QA commented on HIVE-19260: | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 8s{color} | {color:red} /data/hiveptest/logs/PreCommit-HIVE-Build-10481/patches/PreCommit-HIVE-Build-10481.patch does not apply to master. Rebase required? Wrong Branch? See http://cwiki.apache.org/confluence/display/Hive/HowToContribute for help. {color} | \\ \\ || Subsystem || Report/Notes || | Console output | http://104.198.109.242/logs//PreCommit-HIVE-Build-10481/yetus.txt | | Powered by | Apache Yetushttp://yetus.apache.org | This message was automatically generated. > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Attachments: HIVE-19260.01-branch-3.patch, HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452324#comment-16452324 ] Hive QA commented on HIVE-19260: Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12920484/HIVE-19260.01-branch-3.patch {color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified. {color:red}ERROR:{color} -1 due to 60 failed/errored test(s), 14128 tests executed *Failed tests:* {noformat} TestBeeLineDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=253) TestDummy - did not produce a TEST-*.xml file (likely timed out) (batchId=253) TestMiniDruidCliDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=253) TestMiniDruidKafkaCliDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=253) TestNonCatCallsWithCatalog - did not produce a TEST-*.xml file (likely timed out) (batchId=217) TestTezPerfCliDriver - did not produce a TEST-*.xml file (likely timed out) (batchId=253) org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[acid_nullscan] (batchId=68) org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[acid_table_stats] (batchId=54) org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[autoColumnStats_4] (batchId=13) org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[row__id] (batchId=80) org.apache.hadoop.hive.cli.TestMiniLlapCliDriver.testCliDriver[acid_bucket_pruning] (batchId=150) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[acid_vectorization_original] (batchId=173) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[check_constraint] (batchId=158) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[default_constraint] (batchId=163) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[dynpart_sort_optimization_acid] (batchId=165) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[enforce_constraint_notnull] (batchId=158) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[insert_values_orig_table_use_metadata] (batchId=169) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[llap_smb] (batchId=176) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[materialized_view_create_rewrite_4] (batchId=157) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[materialized_view_create_rewrite_5] (batchId=154) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[mergejoin] (batchId=169) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[sysdb] (batchId=163) org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[tez_smb_1] (batchId=172) org.apache.hadoop.hive.cli.TestMiniSparkOnYarnCliDriver.testCliDriver[bucketizedhiveinputformat] (batchId=183) org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[acid_vectorization_original_tez] (batchId=106) org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_5] (batchId=105) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[avro_non_nullable_union] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[cachingprintstream] (batchId=95) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[compute_stats_long] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[dyn_part3] (batchId=95) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[dyn_part_max_per_node] (batchId=95) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[dynamic_partitions_with_whitelist] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[script_broken_pipe2] (batchId=95) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[script_broken_pipe3] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[script_error] (batchId=95) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[serde_regex2] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[stats_aggregator_error_2] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[stats_publisher_error_1] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[stats_publisher_error_2] (batchId=95) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_corr_in_agg] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_in_implicit_gby] (batchId=95) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_notin_implicit_gby] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_scalar_corr_multi_rows] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.testCliDriver[subquery_scalar_multi_rows] (batchId=96) org.apache.hadoop.hive.cli.TestNegativeCliDriver.te
[jira] [Commented] (HIVE-19260) Streaming Ingest API doesn't normalize db.table names
[ https://issues.apache.org/jira/browse/HIVE-19260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452978#comment-16452978 ] Eugene Koifman commented on HIVE-19260: --- committed to branch-3 > Streaming Ingest API doesn't normalize db.table names > - > > Key: HIVE-19260 > URL: https://issues.apache.org/jira/browse/HIVE-19260 > Project: Hive > Issue Type: Bug > Components: HCatalog, Streaming, Transactions >Affects Versions: 0.13 >Reporter: Eugene Koifman >Assignee: Eugene Koifman >Priority: Blocker > Fix For: 3.0.0 > > Attachments: HIVE-19260.01-branch-3.patch, HIVE-19260.01.patch > > > Hive is case insensitive wrt db/table names. These gets normalized to lower > case for SQL processing. > When HiveEndPoint is created it uses db.table strings as is, and they end up > propagated this way to transaction metadata tables in the metastore via lock > acquisition. This makes them look like different tables in Cleaner and lock > manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)