[jira] [Updated] (HIVE-5391) make ORC predicate pushdown work with vectorization
[ https://issues.apache.org/jira/browse/HIVE-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-5391: --- Resolution: Fixed Fix Version/s: 0.13.0 Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Sergey! > make ORC predicate pushdown work with vectorization > --- > > Key: HIVE-5391 > URL: https://issues.apache.org/jira/browse/HIVE-5391 > Project: Hive > Issue Type: Improvement >Reporter: Sergey Shelukhin >Assignee: Sergey Shelukhin > Fix For: 0.13.0 > > Attachments: HIVE-5391.01.patch, HIVE-5391.01-vectorization.patch, > HIVE-5391.02.patch, HIVE-5391.03.patch, HIVE-5391.patch, > HIVE-5391-vectorization.patch > > > Vectorized execution doesn't utilize ORC predicate pushdown. It should. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5372) Refactor TypeInfo and PrimitiveTypeEntry class hierachy to eliminate info repetition
[ https://issues.apache.org/jira/browse/HIVE-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Chauhan updated HIVE-5372: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk. Thanks, Xuefu! > Refactor TypeInfo and PrimitiveTypeEntry class hierachy to eliminate info > repetition > > > Key: HIVE-5372 > URL: https://issues.apache.org/jira/browse/HIVE-5372 > Project: Hive > Issue Type: Improvement > Components: Types >Affects Versions: 0.12.0 >Reporter: Xuefu Zhang >Assignee: Xuefu Zhang > Fix For: 0.13.0 > > Attachments: HIVE-5372.1.patch, HIVE-5372.2.patch, HIVE-5372.3.patch, > HIVE-5372.4.patch, HIVE-5372.patch > > > TypeInfo with its sub-classes and PrimititiveTypeEntry class seem having > repetitive information, such as type names and type params. It will be good > if we can streamline the information organization. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
[
https://issues.apache.org/jira/browse/HIVE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787931#comment-13787931
]
Hive QA commented on HIVE-5460:
---
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12607123/HIVE-5460.1.patch.txt
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 4060 tests executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_script_broken_pipe1
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1064/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1064/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
> invalid offsets in lag lead should return an exception (per ISO-SQL)
> -
>
> Key: HIVE-5460
> URL: https://issues.apache.org/jira/browse/HIVE-5460
> Project: Hive
> Issue Type: Bug
>Affects Versions: 0.11.0
>Reporter: N Campbell
>Assignee: Edward Capriolo
>Priority: Minor
> Attachments: HIVE-5460.1.patch.txt
>
>
> ISO-SQL 2011 defines how lag and lead should behave when invalid offsets are
> provided to the functions.
> i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by
> tint.rnum) from tint tint
> Instead of a meaningful error (as other vendors will emit) you get
> Error: Query returned non-zero code: 2, cause: FAILED: Execution Error,
> return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask
> SQLState: 08S01
> ErrorCode: 2
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
[ https://issues.apache.org/jira/browse/HIVE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated HIVE-5460: -- Status: Patch Available (was: Open) Should test. > invalid offsets in lag lead should return an exception (per ISO-SQL) > - > > Key: HIVE-5460 > URL: https://issues.apache.org/jira/browse/HIVE-5460 > Project: Hive > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: N Campbell >Assignee: Edward Capriolo >Priority: Minor > Attachments: HIVE-5460.1.patch.txt > > > ISO-SQL 2011 defines how lag and lead should behave when invalid offsets are > provided to the functions. > i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by > tint.rnum) from tint tint > Instead of a meaningful error (as other vendors will emit) you get > Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, > return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask > SQLState: 08S01 > ErrorCode: 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
[ https://issues.apache.org/jira/browse/HIVE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated HIVE-5460: -- Attachment: HIVE-5460.1.patch.txt > invalid offsets in lag lead should return an exception (per ISO-SQL) > - > > Key: HIVE-5460 > URL: https://issues.apache.org/jira/browse/HIVE-5460 > Project: Hive > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: N Campbell >Assignee: Edward Capriolo >Priority: Minor > Attachments: HIVE-5460.1.patch.txt > > > ISO-SQL 2011 defines how lag and lead should behave when invalid offsets are > provided to the functions. > i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by > tint.rnum) from tint tint > Instead of a meaningful error (as other vendors will emit) you get > Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, > return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask > SQLState: 08S01 > ErrorCode: 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-2436) Update project naming and description in Hive website
[ https://issues.apache.org/jira/browse/HIVE-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787892#comment-13787892 ] Carl Steinbach commented on HIVE-2436: -- +1 > Update project naming and description in Hive website > - > > Key: HIVE-2436 > URL: https://issues.apache.org/jira/browse/HIVE-2436 > Project: Hive > Issue Type: Sub-task >Reporter: John Sichi >Assignee: Brock Noland > Attachments: HIVE-2436.patch > > > http://www.apache.org/foundation/marks/pmcs.html#naming -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5087) Rename npath UDF to matchpath
[ https://issues.apache.org/jira/browse/HIVE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787888#comment-13787888 ] Hudson commented on HIVE-5087: -- ABORTED: Integrated in Hive-branch-0.12-hadoop1 #15 (See [https://builds.apache.org/job/Hive-branch-0.12-hadoop1/15/]) HIVE-5087 : Rename npath UDF to matchpath (Edward Capriolo and Carl Steinbach via Ashutosh Chauhan) (thejas: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1529577) * /hive/branches/branch-0.12/ql/src/java/org/apache/hadoop/hive/ql/exec/FunctionRegistry.java * /hive/branches/branch-0.12/ql/src/java/org/apache/hadoop/hive/ql/udf/ptf/MatchPath.java * /hive/branches/branch-0.12/ql/src/java/org/apache/hadoop/hive/ql/udf/ptf/NPath.java * /hive/branches/branch-0.12/ql/src/test/queries/clientpositive/ptf_matchpath.q * /hive/branches/branch-0.12/ql/src/test/queries/clientpositive/ptf_npath.q * /hive/branches/branch-0.12/ql/src/test/queries/clientpositive/ptf_register_tblfn.q * /hive/branches/branch-0.12/ql/src/test/results/clientpositive/ptf_matchpath.q.out * /hive/branches/branch-0.12/ql/src/test/results/clientpositive/ptf_npath.q.out * /hive/branches/branch-0.12/ql/src/test/results/clientpositive/ptf_register_tblfn.q.out * /hive/branches/branch-0.12/ql/src/test/results/clientpositive/show_functions.q.out > Rename npath UDF to matchpath > - > > Key: HIVE-5087 > URL: https://issues.apache.org/jira/browse/HIVE-5087 > Project: Hive > Issue Type: Bug >Reporter: Edward Capriolo >Assignee: Edward Capriolo >Priority: Blocker > Fix For: 0.12.0 > > Attachments: HIVE-5087.1.patch.txt, HIVE-5087.2.patch, > HIVE-5087.99.patch.txt, HIVE-5087-branch0.12.2.patch, > HIVE-5087-matchpath.1.patch.txt, HIVE-5087-matchpath.2.patch, > HIVE-5087.patch.txt, HIVE-5087.patch.txt, regex_path.diff > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5019) Use StringBuffer instead of += (issue 1)
[ https://issues.apache.org/jira/browse/HIVE-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5019: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Use StringBuffer instead of += (issue 1) > > > Key: HIVE-5019 > URL: https://issues.apache.org/jira/browse/HIVE-5019 > Project: Hive > Issue Type: Sub-task >Reporter: Benjamin Jakobus >Assignee: Benjamin Jakobus > Attachments: HIVE-5019.2.patch.txt, HIVE-5019.3.patch.txt > > > Issue 1 - use of StringBuilder over += inside loops. > java/org/apache/hadoop/hive/ql/optimizer/physical/GenMRSkewJoinProcessor.java > java/org/apache/hadoop/hive/ql/optimizer/ppr/PartitionPruner.java > java/org/apache/hadoop/hive/ql/parse/PTFTranslator.java > java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java > java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java > java/org/apache/hadoop/hive/ql/plan/ConditionalResolverMergeFiles.java > java/org/apache/hadoop/hive/ql/plan/PlanUtils.java > java/org/apache/hadoop/hive/ql/security/authorization/BitSetCheckedAuthorizationProvider.java > java/org/apache/hadoop/hive/ql/stats/jdbc/JDBCStatsUtils.java > java/org/apache/hadoop/hive/ql/udf/UDFLike.java > java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFSentences.java > java/org/apache/hadoop/hive/ql/udf/generic/NumDistinctValueEstimator.java > java/org/apache/hadoop/hive/ql/udf/ptf/NPath.java -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4969) HCatalog HBaseHCatStorageHandler is not returning all the data
[
https://issues.apache.org/jira/browse/HIVE-4969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thejas M Nair updated HIVE-4969:
Fix Version/s: (was: 0.11.1)
(was: 0.12.0)
Preparing for 0.12 release. Removing fix version of 0.12 for those that are not
in 0.12 branch.
> HCatalog HBaseHCatStorageHandler is not returning all the data
> --
>
> Key: HIVE-4969
> URL: https://issues.apache.org/jira/browse/HIVE-4969
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 0.11.0
>Reporter: Venki Korukanti
>Priority: Critical
> Attachments: HIVE-4969-1.patch
>
>
> Repro steps:
> 1) Create an HCatalog table mapped to HBase table.
> hcat -e "CREATE TABLE studentHCat(rownum int, name string, age int, gpa float)
> STORED BY 'org.apache.hcatalog.hbase.HBaseHCatStorageHandler'
> TBLPROPERTIES('hbase.table.name' ='studentHBase',
>'hbase.columns.mapping' =
> ':key,onecf:name,twocf:age,threecf:gpa')";
> 2) Load the following data from Pig.
> cat student_data
> 1^Asarah laertes^A23^A2.40
> 2^Atom allen^A72^A1.57
> 3^Abob ovid^A61^A2.67
> 4^Aethan nixon^A38^A2.15
> 5^Acalvin robinson^A28^A2.53
> 6^Airene ovid^A65^A2.56
> 7^Ayuri garcia^A36^A1.65
> 8^Acalvin nixon^A41^A1.04
> 9^Ajessica davidson^A48^A2.11
> 10^Akatie king^A39^A1.05
> grunt> A = LOAD 'student_data' AS
> (rownum:int,name:chararray,age:int,gpa:float);
> grunt> STORE A INTO 'studentHCat' USING org.apache.hcatalog.pig.HCatStorer();
> 3) Now from HBase do a scan on the studentHBase table
> hbase(main):026:0> scan 'studentPig', {LIMIT => 5}
> 4) From pig access the data in table
> grunt> A = LOAD 'studentHCat' USING org.apache.hcatalog.pig.HCatLoader();
> grunt> STORE A INTO '/user/root/studentPig';
> 5) Verify the output written in StudentPig
> hadoop fs -cat /user/root/studentPig/part-r-0
> 1 23
> 2 72
> 3 61
> 4 38
> 5 28
> 6 65
> 7 36
> 8 41
> 9 48
> 10 39
> The data returned has only two fields (rownum and age).
> Problem:
> While reading the data from HBase table, HbaseSnapshotRecordReader gets data
> row in Result (org.apache.hadoop.hbase.client.Result) object and processes
> the KeyValue fields in it. After processing, it creates another Result object
> out of the processed KeyValue array. Problem here is KeyValue array is not
> sorted. Result object expects the input KeyValue array to have sorted
> elements. When we call the Result.getValue() it returns no value for some of
> the fields as it does a binary search on un-ordered array.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5215) The optional methods in JDBC API implementations should throw a SQLFeatureNotSupportedException instead of SQLException
[ https://issues.apache.org/jira/browse/HIVE-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5215: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > The optional methods in JDBC API implementations should throw a > SQLFeatureNotSupportedException instead of SQLException > > > Key: HIVE-5215 > URL: https://issues.apache.org/jira/browse/HIVE-5215 > Project: Hive > Issue Type: Bug > Components: JDBC >Reporter: Vaibhav Gumashta >Priority: Minor > > The optional methods in JDBC API implementations should throw a > SQLFeatureNotSupportedException instead of SQLException. This is per JDBC > standards. > From the jdbc 4.1 specs: > "If a JDBC driver does not support or only provides partial support for an > optional feature, the corresponding DatabaseMetaData method must indicate the > feature is not supported. Any methods for a feature that is not implemented > are required to throw a SQLFeatureNotSupportedException." -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5384) hcatloadstore.pig should be upgraded to org.apache.hive.hcatalog.pig.HCatLoader
[ https://issues.apache.org/jira/browse/HIVE-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5384: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > hcatloadstore.pig should be upgraded to > org.apache.hive.hcatalog.pig.HCatLoader > --- > > Key: HIVE-5384 > URL: https://issues.apache.org/jira/browse/HIVE-5384 > Project: Hive > Issue Type: Bug > Components: WebHCat >Affects Versions: 0.12.0 >Reporter: Eugene Koifman >Assignee: Eugene Koifman > > this was missed in HIVE-4869 > actually we should probably clone the test and also keep a version that uses > old package name until Hive 0.14 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4777) Null value Versus RuntimeException in failed data type converting
[
https://issues.apache.org/jira/browse/HIVE-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thejas M Nair updated HIVE-4777:
Fix Version/s: (was: 0.12.0)
Preparing for 0.12 release. Removing fix version of 0.12 for those that are not
in 0.12 branch.
> Null value Versus RuntimeException in failed data type converting
> -
>
> Key: HIVE-4777
> URL: https://issues.apache.org/jira/browse/HIVE-4777
> Project: Hive
> Issue Type: Improvement
> Components: Serializers/Deserializers
>Reporter: Cheng Hao
>Priority: Minor
>
> Usually "null" value will returns if the data can not be converted to the
> other type. (e.g. null == doubleConverter.convert("abc")).
> But it also may also throws RuntimeException other than NumberFormatException
> in the DoubleConverter.convert() method, as the type BINARY can not be
> converted into DOUBLE. And there are some others. (Check
> PrimitiveObjectInspectorUtils.java for details.)
> It's acceptable for throwing exception, but may not in runtime, as the data
> type convertibility can be decided before the data arrives. The earlier stage
> the better.
> Or just like the normal case, return null constantly for the in-convertible
> data types converting.
> What do you think?
> Thanks,
> Hao
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-4446) [HCatalog] Documentation for HIVE-4442, HIVE-4443, HIVE-4444
[ https://issues.apache.org/jira/browse/HIVE-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4446: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > [HCatalog] Documentation for HIVE-4442, HIVE-4443, HIVE- > > > Key: HIVE-4446 > URL: https://issues.apache.org/jira/browse/HIVE-4446 > Project: Hive > Issue Type: Improvement > Components: HCatalog >Reporter: Daniel Dai >Assignee: Lefty Leverenz > Attachments: HIVE-4446-1.patch > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4577) hive CLI can't handle hadoop dfs command with space and quotes.
[ https://issues.apache.org/jira/browse/HIVE-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4577: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > hive CLI can't handle hadoop dfs command with space and quotes. > > > Key: HIVE-4577 > URL: https://issues.apache.org/jira/browse/HIVE-4577 > Project: Hive > Issue Type: Bug > Components: CLI >Affects Versions: 0.9.0, 0.10.0 >Reporter: Bing Li >Assignee: Bing Li > Attachments: HIVE-4577.1.patch, HIVE-4577.2.patch, > HIVE-4577.3.patch.txt > > > As design, hive could support hadoop dfs command in hive shell, like > hive> dfs -mkdir /user/biadmin/mydir; > but has different behavior with hadoop if the path contains space and quotes > hive> dfs -mkdir "hello"; > drwxr-xr-x - biadmin supergroup 0 2013-04-23 09:40 > /user/biadmin/"hello" > hive> dfs -mkdir 'world'; > drwxr-xr-x - biadmin supergroup 0 2013-04-23 09:43 > /user/biadmin/'world' > hive> dfs -mkdir "bei jing"; > drwxr-xr-x - biadmin supergroup 0 2013-04-23 09:44 > /user/biadmin/"bei > drwxr-xr-x - biadmin supergroup 0 2013-04-23 09:44 > /user/biadmin/jing" -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-3685) TestCliDriver (script_pipe.q) failed with IBM JDK
[ https://issues.apache.org/jira/browse/HIVE-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-3685: Fix Version/s: (was: 0.12.0) (was: 0.9.0) (was: 0.8.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > TestCliDriver (script_pipe.q) failed with IBM JDK > - > > Key: HIVE-3685 > URL: https://issues.apache.org/jira/browse/HIVE-3685 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.7.1, 0.8.0, 0.9.0, 0.11.0 > Environment: ant-1.8.2 > IBM JDK 1.6 >Reporter: Bing Li >Assignee: Bing Li > Attachments: HIVE-3685.1.patch-trunk.txt, HIVE_3685.patch > > > 1 failed: TestCliDriver (script_pipe.q) > [junit] Begin query: script_pipe.q > [junit] java.io.IOException: No such file or directory > [junit] at java.io.FileOutputStream.writeBytes(Native Method) > [junit] at java.io.FileOutputStream.write(FileOutputStream.java:293) > [junit] at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:76) > [junit] at > java.io.BufferedOutputStream.flush(BufferedOutputStream.java:134) > [junit] at > java.io.BufferedOutputStream.flush(BufferedOutputStream.java:135) > [junit] at java.io.DataOutputStream.flush(DataOutputStream.java:117) > [junit] at > org.apache.hadoop.hive.ql.exec.TextRecordWriter.close(TextRecordWriter.java:48) > [junit] at > org.apache.hadoop.hive.ql.exec.ScriptOperator.close(ScriptOperator.java:365) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.ExecReducer.close(ExecReducer.java:303) > [junit] at > org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:473) > [junit] at > org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:411) > [junit] at > org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:216) > [junit] org.apache.hadoop.hive.ql.metadata.HiveException: Hit error while > closing .. > [junit] at > org.apache.hadoop.hive.ql.exec.ScriptOperator.close(ScriptOperator.java:452) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.ExecReducer.close(ExecReducer.java:303) > [junit] at > org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:473) > [junit] at > org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:411) > [junit] at > org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:216) > [junit] org.apache.hadoop.hive.ql.metadata.HiveException: Hit error while > closing .. > [junit] at > org.apache.hadoop.hive.ql.exec.ScriptOperator.close(ScriptOperator.java:452) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.ExecReducer.close(ExecReducer.java:303) > [junit] at > org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:473) > [junit] at > org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:411) > [junit] at > org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:216) > [junit] org.apache.hadoop.hive.ql.metadata.HiveException: Hit error while > closing .. > [junit] at > org.apache.hadoop.hive.ql.exec.ScriptOperator.close(ScriptOperator.java:452) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.Operator.close(Operator.java:566) > [junit] at > org.apache.hadoop.hive.ql.exec.ExecReducer.close(ExecReducer.java:303) > [junit] at > org.apache.hadoop.mapred.ReduceTask.runOldReducer(ReduceTask.java:473) > [junit] at > org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:411) > [junit] at > org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:216) > [junit] Ended Job = job_local_0001 with errors > [junit
[jira] [Updated] (HIVE-5044) StringUtils
[
https://issues.apache.org/jira/browse/HIVE-5044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thejas M Nair updated HIVE-5044:
Fix Version/s: (was: 0.12.0)
Preparing for 0.12 release. Removing fix version of 0.12 for those that are not
in 0.12 branch.
> StringUtils
> ---
>
> Key: HIVE-5044
> URL: https://issues.apache.org/jira/browse/HIVE-5044
> Project: Hive
> Issue Type: Sub-task
>Reporter: Benjamin Jakobus
>Assignee: Benjamin Jakobus
>
> When you see code like this:
> first = true;
> for (int k = 0; k < columnSize; k++) {
> String newColName = i + "VALUE" + k; // any name, it does not matter.
> + newColName = i + "VALUE" + k; // any name, it does not matter.
> if (!first)
> Unknown macro: { - valueColNames = valueColNames + ","; - valueColTypes =
> valueColTypes + ","; + valueColNames.append(","); +
> valueColTypes.append(","); }
> valueColNames = valueColNames + newColName;
> valueColTypes = valueColTypes + valueCols.get(k).getTypeString();
> + valueColNames.append(newColName);
> + valueColTypes.append(valueCols.get(k).getTypeString());
> first = false;
> Can you replace it with StringUtil.join()
> I have seen this about 4 places in hive.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5009) Fix minor optimization issues
[
https://issues.apache.org/jira/browse/HIVE-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thejas M Nair updated HIVE-5009:
Fix Version/s: (was: 0.12.0)
Preparing for 0.12 release. Removing fix version of 0.12 for those that are not
in 0.12 branch.
> Fix minor optimization issues
> -
>
> Key: HIVE-5009
> URL: https://issues.apache.org/jira/browse/HIVE-5009
> Project: Hive
> Issue Type: Improvement
>Reporter: Benjamin Jakobus
>Assignee: Benjamin Jakobus
>Priority: Minor
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> I have found some minor optimization issues in the codebase, which I would
> like to rectify and contribute. Specifically, these are:
> The optimizations that could be applied to Hive's code base are as follows:
> 1. Use StringBuffer when appending strings - In 184 instances, the
> concatination operator (+=) was used when appending strings. This is
> inherintly inefficient - instead Java's StringBuffer or StringBuilder class
> should be used. 12 instances of this optimization can be applied to the
> GenMRSkewJoinProcessor class and another three to the optimizer. CliDriver
> uses the + operator inside a loop, so does the column projection utilities
> class (ColumnProjectionUtils) and the aforementioned skew-join processor.
> Tests showed that using the StringBuilder when appending strings is 57\%
> faster than using the + operator (using the StringBuffer took 122
> milliseconds whilst the + operator took 284 milliseconds). The reason as to
> why using the StringBuffer class is preferred over using the + operator, is
> because
> String third = first + second;
> gets compiled to:
> StringBuilder builder = new StringBuilder( first );
> builder.append( second );
> third = builder.toString();
> Therefore, when building complex strings, that, for example involve loops,
> require many instantiations (and as discussed below, creating new objects
> inside loops is inefficient).
> 2. Use arrays instead of List - Java's java.util.Arrays class asList method
> is a more efficient at creating creating lists from arrays than using loops
> to manually iterate over the elements (using asList is computationally very
> cheap, O(1), as it merely creates a wrapper object around the array; looping
> through the list however has a complexity of O(n) since a new list is created
> and every element in the array is added to this new list). As confirmed by
> the experiment detailed in Appendix D, the Java compiler does not
> automatically optimize and replace tight-loop copying with asList: the
> loop-copying of 1,000,000 items took 15 milliseconds whilst using asList is
> instant.
> Four instances of this optimization can be applied to Hive's codebase (two of
> these should be applied to the Map-Join container - MapJoinRowContainer) -
> lines 92 to 98:
> for (obj = other.first(); obj != null; obj = other.next()) {
> ArrayList ele = new ArrayList(obj.length);
> for (int i = 0; i < obj.length; i++) {
> ele.add(obj[i]);
> }
> list.add((Row) ele);
> }
> 3. Unnecessary wrapper object creation - In 31 cases, wrapper object creation
> could be avoided by simply using the provided static conversion methods. As
> noted in the PMD documentation, "using these avoids the cost of creating
> objects that also need to be garbage-collected later."
> For example, line 587 of the SemanticAnalyzer class, could be replaced by the
> more efficient parseDouble method call:
> // Inefficient:
> Double percent = Double.valueOf(value).doubleValue();
> // To be replaced by:
> Double percent = Double.parseDouble(value);
> Our test case in Appendix D confirms this: converting 10,000 strings into
> integers using Integer.parseInt(gen.nextSessionId()) (i.e. creating an
> unnecessary wrapper object) took 119 on average; using parseInt() took only
> 38. Therefore creating even just one unnecessary wrapper object can make your
> code up to 68% slower.
> 4. Converting literals to strings using + "" - Converting literals to strings
> using + "" is quite inefficient (see Appendix D) and should be done by
> calling the toString() method instead: converting 1,000,000 integers to
> strings using + "" took, on average, 1340 milliseconds whilst using the
> toString() method only required 1183 milliseconds (hence adding empty strings
> takes nearly 12% more time).
> 89 instances of this using + "" when converting literals were found in Hive's
> codebase - one of these are found in the JoinUtil.
> 5. Avoid manual copying of arrays - Instead of copying arrays as is done in
> GroupByOperator on line 1040 (see below), the more efficient System.arraycopy
> can be used (arraycopy is a native method meaning that the entire memory
> block is copied using memcpy or mmove).
> // Line 1
[jira] [Updated] (HIVE-5295) HiveConnection#configureConnection tries to execute statement even after it is closed
[ https://issues.apache.org/jira/browse/HIVE-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5295: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > HiveConnection#configureConnection tries to execute statement even after it > is closed > - > > Key: HIVE-5295 > URL: https://issues.apache.org/jira/browse/HIVE-5295 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Vaibhav Gumashta >Assignee: Vaibhav Gumashta > Attachments: D12957.1.patch, D12957.2.patch, D12957.3.patch, > HIVE-5295.D12957.3.patch, HIVE-5295.D12957.3.patch, HIVE-5295.D12957.4.patch > > > HiveConnection#configureConnection tries to execute statement even after it > is closed. For remote JDBC client, it tries to set the conf var using 'set > foo=bar' by calling HiveStatement.execute for each conf var pair, but closes > the statement after the 1st iteration through the conf var pairs. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4978) [WebHCat] Close the PrintWriter after writing data
[ https://issues.apache.org/jira/browse/HIVE-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4978: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > [WebHCat] Close the PrintWriter after writing data > -- > > Key: HIVE-4978 > URL: https://issues.apache.org/jira/browse/HIVE-4978 > Project: Hive > Issue Type: Bug > Components: HCatalog >Affects Versions: 0.11.0 >Reporter: Venki Korukanti >Priority: Minor > Attachments: HIVE-4978-1.patch, HIVE-4978-2.patch > > > We are not closing the PrintWriter after writing data into it. I haven't seen > any problems so far, but it is good to close the PrintWriter so that > resources are released properly. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4752) Add support for hs2 api to use thrift over http
[ https://issues.apache.org/jira/browse/HIVE-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4752: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Add support for hs2 api to use thrift over http > --- > > Key: HIVE-4752 > URL: https://issues.apache.org/jira/browse/HIVE-4752 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Thejas M Nair > > Hiveserver2 acts as service on the cluster for external applications. One way > to implement access control to services on a hadoop cluster to have a gateway > server authorizes service requests before forwarding them to the server. The > [knox project | http://wiki.apache.org/incubator/knox] has taken this > approach to simplify cluster security management. > Other services on hadoop cluster such as webhdfs and webhcat already use > HTTP. Having hiveserver2 also support thrift over http transport will enable > securing hiveserver2 as well using the same approach. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4738) Compiler should captures addional read/write entities for non-select statements
[ https://issues.apache.org/jira/browse/HIVE-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4738: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Compiler should captures addional read/write entities for non-select > statements > > > Key: HIVE-4738 > URL: https://issues.apache.org/jira/browse/HIVE-4738 > Project: Hive > Issue Type: Bug > Components: Query Processor >Affects Versions: 0.11.0 >Reporter: Prasad Mujumdar >Assignee: Prasad Mujumdar > Attachments: HIVE-4738-1.patch, HIVE-4738-2.patch > > > - The describe table statement should include the source table in the read > entity. > - Create view should include tables referred in the view in the read entity. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5092) Fix hiveserver2 mapreduce local job on Windows
[
https://issues.apache.org/jira/browse/HIVE-5092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thejas M Nair updated HIVE-5092:
Fix Version/s: (was: 0.12.0)
Preparing for 0.12 release. Removing fix version of 0.12 for those that are not
in 0.12 branch.
> Fix hiveserver2 mapreduce local job on Windows
> --
>
> Key: HIVE-5092
> URL: https://issues.apache.org/jira/browse/HIVE-5092
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, Windows
>Reporter: Daniel Dai
>Assignee: Daniel Dai
> Attachments: HIVE-5092-1.patch
>
>
> Hiveserver2 fail on Mapreduce local job fail. For example:
> {code}
> select /*+ MAPJOIN(v) */ registration from studenttab10k s join votertab10k v
> on (s.name = v.name);
> {code}
> The root cause is "class not found" in the local hadoop job
> (MapredLocalTask.execute). HADOOP_CLASSPATH does not include $HIVE_HOME/lib.
> Set HADOOP_CLASSPATH correctly will fix the issue.
> However, there is one complexity in Windows. We start Hiveserver2 using
> Windows service console (services.msc), which takes hiveserver2.xml generated
> by hive.cmd. There is no way to pass environment variable in hiveserver2.xml
> (weird but reality). I attach a patch which pass it through command line
> arguments and relay to HADOOP_CLASSPATH in Hive code.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-4703) Describe on a table returns "from deserializer" for column comments instead of values supplied in Create Table
[
https://issues.apache.org/jira/browse/HIVE-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thejas M Nair updated HIVE-4703:
Fix Version/s: (was: 0.12.0)
Preparing for 0.12 release. Removing fix version of 0.12 for those that are not
in 0.12 branch.
> Describe on a table returns "from deserializer" for column comments instead
> of values supplied in Create Table
> --
>
> Key: HIVE-4703
> URL: https://issues.apache.org/jira/browse/HIVE-4703
> Project: Hive
> Issue Type: Bug
>Affects Versions: 0.12.0
>Reporter: Eugene Koifman
> Attachments: webhcatMini.sh
>
>
> This causes Templeton e2e tests to fail.
> start WeHcat server (build/dist/hcatalog/sbin/webhcat_server.sh start)
> run commands in the attached webhcatMini.sh.
> It creates a table with some comments on columns.
> When executing describe (GET) on this table, original comments are lost and
> are replaced with "from deserializer" string.
> Here is the output of these commands:
> localhost:dev ekoifman$ webhcatMini.sh
> Running delete test_table ifExists
> HTTP/1.1 200 OK
> Set-Cookie:
> hadoop.auth="u=ekoifman&p=ekoifman&t=simple&e=1370945567179&s=vIBKhGQwzs5pPAY3IkhyPpDkWrY=";Version=1;Path=/;Discard
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Type: application/json
> Transfer-Encoding: chunked
> Server: Jetty(7.6.0.v20120127)
> {"table":"test_table","database":"default"}
> Running create test_table
> HTTP/1.1 200 OK
> Set-Cookie:
> hadoop.auth="u=ekoifman&p=ekoifman&t=simple&e=1370945569788&s=g37NbyyRnf667IciUiIpIQNYGOo=";Version=1;Path=/;Discard
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Type: application/json
> Transfer-Encoding: chunked
> Server: Jetty(7.6.0.v20120127)
> {"table":"test_table","database":"default"}
> Running describe test_table
> HTTP/1.1 200 OK
> Set-Cookie:
> hadoop.auth="u=ekoifman&p=ekoifman&t=simple&e=1370945572423&s=7kE1FOn1Co2JQzZfW0V1myqulw0=";Version=1;Path=/;Discard
> Expires: Thu, 01 Jan 1970 00:00:00 GMT
> Content-Type: application/json
> Transfer-Encoding: chunked
> Server: Jetty(7.6.0.v20120127)
> {"columns":[{"name":"int","comment":"from
> deserializer","type":"string"},{"name":"int2","comment":"from
> deserializer","type":"int"}],"database":"default","table":"test_table"}
> Mon Jun 10 17:12:55 PDT 2013
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5018) Avoiding object instantiation in loops (issue 6)
[ https://issues.apache.org/jira/browse/HIVE-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5018: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Avoiding object instantiation in loops (issue 6) > > > Key: HIVE-5018 > URL: https://issues.apache.org/jira/browse/HIVE-5018 > Project: Hive > Issue Type: Sub-task >Reporter: Benjamin Jakobus >Assignee: Benjamin Jakobus >Priority: Minor > Attachments: HIVE-5018.1.patch.txt > > > Object instantiation inside loops is very expensive. Where possible, object > references should be created outside the loop so that they can be reused. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5193) Columnar Pushdown for RC/ORC File not happening in HCatLoader
[ https://issues.apache.org/jira/browse/HIVE-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5193: Fix Version/s: (was: 0.11.1) (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Columnar Pushdown for RC/ORC File not happening in HCatLoader > -- > > Key: HIVE-5193 > URL: https://issues.apache.org/jira/browse/HIVE-5193 > Project: Hive > Issue Type: Improvement > Components: HCatalog >Affects Versions: 0.10.0, 0.11.0 >Reporter: Viraj Bhat >Assignee: Viraj Bhat > Attachments: HIVE-5193.patch > > > Currently the HCatLoader is not taking advantage of the > ColumnProjectionUtils. where it could skip columns during read. The > information is available in Pig it just needs to get to the Readers. > Viraj -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5248) WebHCat Proxy User Support (HIVE-4601) requires documentation
[ https://issues.apache.org/jira/browse/HIVE-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5248: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > WebHCat Proxy User Support (HIVE-4601) requires documentation > - > > Key: HIVE-5248 > URL: https://issues.apache.org/jira/browse/HIVE-5248 > Project: Hive > Issue Type: Bug > Components: Documentation, WebHCat >Affects Versions: 0.12.0 >Reporter: Eugene Koifman > > This should be documented somewhere as it's a non-trivial feature. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4741) Add Hive config API to modify the restrict list
[ https://issues.apache.org/jira/browse/HIVE-4741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4741: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Add Hive config API to modify the restrict list > --- > > Key: HIVE-4741 > URL: https://issues.apache.org/jira/browse/HIVE-4741 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.11.0 >Reporter: Prasad Mujumdar >Assignee: Prasad Mujumdar > Attachments: HIVE-4741-1.patch > > > HiveConf supports a restrict list configuration which is a black list of > configurations that can be modified through the 'set x=y'. This is especially > useful for HiveServer2 to restrict clients from overriding some of server > configurations. > Currently the restrict list value can't be changed after the HiveConf object > is instantiated. It would be useful for custom code like Hooks to have a way > to be able to update that setting. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4734) Use custom ObjectInspectors for AvroSerde
[ https://issues.apache.org/jira/browse/HIVE-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4734: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Use custom ObjectInspectors for AvroSerde > - > > Key: HIVE-4734 > URL: https://issues.apache.org/jira/browse/HIVE-4734 > Project: Hive > Issue Type: Improvement > Components: Serializers/Deserializers >Reporter: Mark Wagner >Assignee: Mark Wagner > Attachments: HIVE-4734.1.patch, HIVE-4734.2.patch, HIVE-4734.3.patch, > HIVE-4734.4.patch, HIVE-4734.5.patch > > > Currently, the AvroSerde recursively copies all fields of a record from the > GenericRecord to a List row object and provides the standard > ObjectInspectors. Performance can be improved by providing ObjectInspectors > to the Avro record itself. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5453) jobsubmission2.conf should use 'timeout' property
[ https://issues.apache.org/jira/browse/HIVE-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5453: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > jobsubmission2.conf should use 'timeout' property > - > > Key: HIVE-5453 > URL: https://issues.apache.org/jira/browse/HIVE-5453 > Project: Hive > Issue Type: Bug > Components: WebHCat >Affects Versions: 0.12.0 >Reporter: Eugene Koifman >Assignee: Eugene Koifman > Attachments: HIVE-5453.patch > > > TestDriverCurl.pm used to support timeout_seconds, which got renamed to > 'timeout'. This makes TestHeartbeat test fail -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5088) Fix udf_translate.q on Windows
[ https://issues.apache.org/jira/browse/HIVE-5088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5088: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Fix udf_translate.q on Windows > -- > > Key: HIVE-5088 > URL: https://issues.apache.org/jira/browse/HIVE-5088 > Project: Hive > Issue Type: Bug > Components: Tests, Windows >Reporter: Daniel Dai >Assignee: Daniel Dai > Attachments: HIVE-5088-1.patch > > > Test failed with message: > [junit] Begin query: udf_translate.q > [junit] 13/08/14 03:23:57 FATAL conf.Configuration: error parsing conf > file: > com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: > Invalid byte 1 of 1-byte UTF-8 sequence. > [junit] Exception in thread "main" java.lang.RuntimeException: > com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: > Invalid byte 1 of 1-byte UTF-8 sequence. > [junit] at > org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1255) > [junit] at > org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:1117) > [junit] at > org.apache.hadoop.conf.Configuration.getProps(Configuration.java:1053) > [junit] at > org.apache.hadoop.conf.Configuration.get(Configuration.java:397) > [junit] at > org.apache.hadoop.conf.Configuration.getBoolean(Configuration.java:594) > [junit] at > org.apache.hadoop.hive.conf.HiveConf.getBoolVar(HiveConf.java:1015) > [junit] at > org.apache.hadoop.hive.ql.exec.mr.ExecDriver.main(ExecDriver.java:659) > [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > [junit] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > [junit] at java.lang.reflect.Method.invoke(Method.java:597) > [junit] at org.apache.hadoop.util.RunJar.main(RunJar.java:160) > [junit] Caused by: > com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: > Invalid byte 1 of 1-byte UTF-8 sequence. > [junit] at > com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(UTF8Reader.java:684) > [junit] at > com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(UTF8Reader.java:554) > [junit] at > com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(XMLEntityScanner.java:1742) > [junit] at > com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.peekChar(XMLEntityScanner.java:487) > [junit] at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2688) > [junit] at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) > [junit] at > com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) > [junit] at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) > [junit] at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) > [junit] at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) > [junit] at > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) > [junit] at > com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:232) > [junit] at > com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284) > [junit] at > javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124) > [junit] at > org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1181) > [junit] ... 11 more > [junit] Exception: Client Execution failed with error code = 1 > [junit] See build/ql/tmp/hive.log, or try "ant test ... > -Dtest.silent=false" to get more logs. > [junit] junit.framework.AssertionFailedError: Client Execution failed > with error code = 1 > [junit] See build/ql/tmp/hive.log, or try "ant test ... > -Dtest.silent=false" to get more logs. > [junit] at junit.framework.Assert.fail(Assert.java:47) > [junit] at > org.apache.hadoop.hive.cli.TestCliDriver.runTest(TestCliDriver.java:122) > [junit] at > org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_udf_translate(TestCliDriver.java:104) > [junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[jira] [Updated] (HIVE-5037) Avoid manual copying of arrays (issue 5)
[ https://issues.apache.org/jira/browse/HIVE-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5037: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Avoid manual copying of arrays (issue 5) > > > Key: HIVE-5037 > URL: https://issues.apache.org/jira/browse/HIVE-5037 > Project: Hive > Issue Type: Sub-task >Reporter: Benjamin Jakobus >Assignee: Benjamin Jakobus > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-2137) JDBC driver doesn't encode string properly.
[ https://issues.apache.org/jira/browse/HIVE-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-2137: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > JDBC driver doesn't encode string properly. > --- > > Key: HIVE-2137 > URL: https://issues.apache.org/jira/browse/HIVE-2137 > Project: Hive > Issue Type: Bug > Components: JDBC >Affects Versions: 0.9.0 >Reporter: Jin Adachi > Labels: patch > Attachments: HIVE-2137.patch, HIVE-2137.patch, HIVE-2137.patch > > > JDBC driver for HiveServer1 decodes string by client side default encoding, > which depends on operating system unless we don't specify another encoding. > It ignore server side encoding. > For example, > when server side operating system and encoding are Linux (utf-8) and client > side operating system and encoding are Windows (shift-jis : it's japanese > charset, makes character corruption happens in the client. > In current implementation of Hive, UTF-8 appears to be expected in server > side so client side should encode/decode string as UTF-8. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4806) Add more implementations of JDBC API methods to Hive and Hive2 drivers
[ https://issues.apache.org/jira/browse/HIVE-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4806: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Add more implementations of JDBC API methods to Hive and Hive2 drivers > -- > > Key: HIVE-4806 > URL: https://issues.apache.org/jira/browse/HIVE-4806 > Project: Hive > Issue Type: Improvement > Components: JDBC >Affects Versions: 0.11.0 >Reporter: Matt Burgess >Assignee: Matt Burgess > Attachments: HIVE-4806.patch > > > Third-party client software such as Pentaho Data Integration (PDI) uses many > different JDBC API calls when interacting with JDBC data sources. Several of > these calls have not yet been implemented in the Hive and Hive 2 drivers and > by default will throw "Method not supported" SQLExceptions when there could > be default implementations instead. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5002) Loosen readRowIndex visibility in ORC's RecordReaderImpl to package private
[ https://issues.apache.org/jira/browse/HIVE-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5002: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Loosen readRowIndex visibility in ORC's RecordReaderImpl to package private > --- > > Key: HIVE-5002 > URL: https://issues.apache.org/jira/browse/HIVE-5002 > Project: Hive > Issue Type: Bug > Components: File Formats >Affects Versions: 0.12.0 >Reporter: Owen O'Malley >Assignee: Owen O'Malley > Attachments: HIVE-5002.D12015.1.patch > > > Some users want to be able to access the rowIndexes directly from ORC reader > extensions. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4700) default webhcat config still refers to old versions of jar files
[ https://issues.apache.org/jira/browse/HIVE-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4700: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > default webhcat config still refers to old versions of jar files > > > Key: HIVE-4700 > URL: https://issues.apache.org/jira/browse/HIVE-4700 > Project: Hive > Issue Type: Bug > Components: HCatalog >Affects Versions: 0.12.0 >Reporter: Eugene Koifman >Priority: Minor > > some examples: > templeton.jar > env.TEMPLETON_HOME/share/webhcat/svr/webhcat-0.6.0-SNAPSHOT.jar > templeton.hive.path > hive-0.10.0.tar.gz/hive-0.10.0/bin/hive > templeton.hive.properties specifies > hive.metastore.uris=thrift://localhost:9933. This seems odd as default Hive > metastore port is 9083 (HiveMetaStore#DEFAULT_HIVE_METASTORE_PORT)) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4842) Hive parallel test framework 2 needs to summarize failures
[ https://issues.apache.org/jira/browse/HIVE-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-4842: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Hive parallel test framework 2 needs to summarize failures > -- > > Key: HIVE-4842 > URL: https://issues.apache.org/jira/browse/HIVE-4842 > Project: Hive > Issue Type: Improvement > Components: Build Infrastructure >Affects Versions: 0.12.0 >Reporter: Vikram Dixit K >Assignee: Brock Noland >Priority: Minor > > Currently when unit tests are run, there are multiple simple ways to consume > the results. Particularly ant testreport target that generates an html file > for easily locating failures. The ptest2 changes coming from HIVE-4675 is > great for running the tests in parallel but not very easy to figure out the > failing tests. It would be great to have an output similar to that of the > testreport target for easy consumption. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5194) Use asList instead of tight loops
[ https://issues.apache.org/jira/browse/HIVE-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5194: Fix Version/s: (was: 0.12.0) Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch. > Use asList instead of tight loops > - > > Key: HIVE-5194 > URL: https://issues.apache.org/jira/browse/HIVE-5194 > Project: Hive > Issue Type: Sub-task >Reporter: Benjamin Jakobus >Assignee: Benjamin Jakobus > > Using asList instead of tight loops is more efficient. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5474) TestThriftHttpCLIService.testExecuteStatement fails in sequential run
[ https://issues.apache.org/jira/browse/HIVE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787851#comment-13787851 ] Thejas M Nair commented on HIVE-5474: - I also tried running TestThriftHttpCLIService and TestThriftBinaryCLIService in isolation and the failure did not happen. This is a problem caused by state left behind by previous test. I would not consider this to be a blocker for 0.12 release. > TestThriftHttpCLIService.testExecuteStatement fails in sequential run > - > > Key: HIVE-5474 > URL: https://issues.apache.org/jira/browse/HIVE-5474 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Vaibhav Gumashta > > This is seen in hive 0.12 branch sequential test run. > TestThriftHttpCLIService.testExecuteStatement > https://builds.apache.org/job/Hive-branch-0.12-hadoop1/13/testReport/org.apache.hive.service.cli.thrift/TestThriftHttpCLIService/testExecuteStatement/ > stderr has "FAILED: Error in acquiring locks: Locks on the underlying > objects cannot be acquired. retry after some time" -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5253) Create component to compile and jar dynamic code
[ https://issues.apache.org/jira/browse/HIVE-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787849#comment-13787849 ] Brock Noland commented on HIVE-5253: This looks pretty good. Now that HIVE-5400 is in, are their still concerns about this? > Create component to compile and jar dynamic code > > > Key: HIVE-5253 > URL: https://issues.apache.org/jira/browse/HIVE-5253 > Project: Hive > Issue Type: Sub-task >Reporter: Edward Capriolo >Assignee: Edward Capriolo > Attachments: HIVE-5253.10.patch.txt, HIVE-5253.11.patch.txt, > HIVE-5253.1.patch.txt, HIVE-5253.3.patch.txt, HIVE-5253.3.patch.txt, > HIVE-5253.3.patch.txt, HIVE-5253.8.patch.txt, HIVE-5253.9.patch.txt, > HIVE-5253.patch.txt > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5476) Authorization-provider tests fail in sequential run
[ https://issues.apache.org/jira/browse/HIVE-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787846#comment-13787846 ] Thejas M Nair commented on HIVE-5476: - That explains why we don't see the issue with ptest2 runs. This is a test/test execution issue and not a product issue, so it not a release blocker. > Authorization-provider tests fail in sequential run > --- > > Key: HIVE-5476 > URL: https://issues.apache.org/jira/browse/HIVE-5476 > Project: Hive > Issue Type: Bug >Reporter: Thejas M Nair >Assignee: Sushanth Sowmyan > > As seen in 0.12 build with hadoop1 - > https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ > Following tests fail - > >>> org.apache.hadoop.hive.ql.security.TestMetastoreAuthorizationProvider.testSimplePrivileges > >>> 12 sec 1 > >>> org.apache.hadoop.hive.ql.security.TestStorageBasedClientSideAuthorizationProvider.testSimplePrivileges > >>>12 sec 1 > >>> org.apache.hadoop.hive.ql.security.TestStorageBasedMetastoreAuthorizationProvider.testSimplePrivileges > >>> 12 sec 1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5476) Authorization-provider tests fail in sequential run
[ https://issues.apache.org/jira/browse/HIVE-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787844#comment-13787844 ] Sushanth Sowmyan commented on HIVE-5476: Ugh, I know what's happening here. They all use the same dbname/tblname without cleanup. >< > Authorization-provider tests fail in sequential run > --- > > Key: HIVE-5476 > URL: https://issues.apache.org/jira/browse/HIVE-5476 > Project: Hive > Issue Type: Bug >Reporter: Thejas M Nair >Assignee: Sushanth Sowmyan > > As seen in 0.12 build with hadoop1 - > https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ > Following tests fail - > >>> org.apache.hadoop.hive.ql.security.TestMetastoreAuthorizationProvider.testSimplePrivileges > >>> 12 sec 1 > >>> org.apache.hadoop.hive.ql.security.TestStorageBasedClientSideAuthorizationProvider.testSimplePrivileges > >>>12 sec 1 > >>> org.apache.hadoop.hive.ql.security.TestStorageBasedMetastoreAuthorizationProvider.testSimplePrivileges > >>> 12 sec 1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-4907) Allow additional tests cases to be specified with -Dtestcase
[ https://issues.apache.org/jira/browse/HIVE-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787827#comment-13787827 ] Vaibhav Gumashta commented on HIVE-4907: This is a very useful patch. There have been some test issues which have been caught only in the recent sequential run for 0.12 branch (test run before leaving some state behind and affecting the test run later) and this can be used to test such dependencies while developing w/o running the whole test suite. > Allow additional tests cases to be specified with -Dtestcase > > > Key: HIVE-4907 > URL: https://issues.apache.org/jira/browse/HIVE-4907 > Project: Hive > Issue Type: Improvement > Components: Testing Infrastructure >Reporter: Brock Noland > Attachments: HIVE-4907.patch > > > Currently we only allow a single tests case to be specified with -Dtestcase. > It'd be ideal if we could add on additional test cases as this would allow us > to batch the unit tests in ptest2. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5474) TestThriftHttpCLIService.testExecuteStatement fails in sequential run
[ https://issues.apache.org/jira/browse/HIVE-5474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787826#comment-13787826 ] Vaibhav Gumashta commented on HIVE-5474: This looks like a test only issue. I tried connecting with beeline in http mode (note: http currently works in auth: NOSASL and does not support doAs), and it works fine. In the tests, I'm setting lock manager to embedded, but looks like the test run in the previous test case is not releasing the lock on the table. I tried running TestThriftBinaryCLIService and TestThriftHttpCLIService sequentially using the patch in: [HIVE-4907|https://issues.apache.org/jira/browse/HIVE-4907]. However, in my opinion, this should not be a blocker for 0.12. > TestThriftHttpCLIService.testExecuteStatement fails in sequential run > - > > Key: HIVE-5474 > URL: https://issues.apache.org/jira/browse/HIVE-5474 > Project: Hive > Issue Type: Bug > Components: HiveServer2 >Reporter: Thejas M Nair >Assignee: Vaibhav Gumashta > > This is seen in hive 0.12 branch sequential test run. > TestThriftHttpCLIService.testExecuteStatement > https://builds.apache.org/job/Hive-branch-0.12-hadoop1/13/testReport/org.apache.hive.service.cli.thrift/TestThriftHttpCLIService/testExecuteStatement/ > stderr has "FAILED: Error in acquiring locks: Locks on the underlying > objects cannot be acquired. retry after some time" -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5475) TestStatsPublisherEnhanced tests fail in sequential test run
[ https://issues.apache.org/jira/browse/HIVE-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787818#comment-13787818 ] Thejas M Nair commented on HIVE-5475: - This is not reproducible when this test is run in isolation. So some state must be left behind by another test, which is causing this to fail. > TestStatsPublisherEnhanced tests fail in sequential test run > > > Key: HIVE-5475 > URL: https://issues.apache.org/jira/browse/HIVE-5475 > Project: Hive > Issue Type: Bug >Reporter: Thejas M Nair > > As seen in 0.12 build with hadoop1 - > https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ > Following tests fail - > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherOneStat > >>>1.5 sec 1 > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisher > >>> 0.84 sec1 > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdates > >>>0.99 sec1 > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdatesSubsetStatistics > >>>0.93 sec1 > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsAggregatorCleanUp -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5476) Authorization-provider tests fail in sequential run
[ https://issues.apache.org/jira/browse/HIVE-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787795#comment-13787795 ] Thejas M Nair commented on HIVE-5476: - Possibly has same roots as issue - HIVE-5475 > Authorization-provider tests fail in sequential run > --- > > Key: HIVE-5476 > URL: https://issues.apache.org/jira/browse/HIVE-5476 > Project: Hive > Issue Type: Bug >Reporter: Thejas M Nair > > As seen in 0.12 build with hadoop1 - > https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ > Following tests fail - > >>> org.apache.hadoop.hive.ql.security.TestMetastoreAuthorizationProvider.testSimplePrivileges > >>> 12 sec 1 > >>> org.apache.hadoop.hive.ql.security.TestStorageBasedClientSideAuthorizationProvider.testSimplePrivileges > >>>12 sec 1 > >>> org.apache.hadoop.hive.ql.security.TestStorageBasedMetastoreAuthorizationProvider.testSimplePrivileges > >>> 12 sec 1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5476) Authorization-provider tests fail in sequential run
[ https://issues.apache.org/jira/browse/HIVE-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5476: Assignee: Sushanth Sowmyan > Authorization-provider tests fail in sequential run > --- > > Key: HIVE-5476 > URL: https://issues.apache.org/jira/browse/HIVE-5476 > Project: Hive > Issue Type: Bug >Reporter: Thejas M Nair >Assignee: Sushanth Sowmyan > > As seen in 0.12 build with hadoop1 - > https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ > Following tests fail - > >>> org.apache.hadoop.hive.ql.security.TestMetastoreAuthorizationProvider.testSimplePrivileges > >>> 12 sec 1 > >>> org.apache.hadoop.hive.ql.security.TestStorageBasedClientSideAuthorizationProvider.testSimplePrivileges > >>>12 sec 1 > >>> org.apache.hadoop.hive.ql.security.TestStorageBasedMetastoreAuthorizationProvider.testSimplePrivileges > >>> 12 sec 1 > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5476) Authorization-provider tests fail in sequential run
Thejas M Nair created HIVE-5476: --- Summary: Authorization-provider tests fail in sequential run Key: HIVE-5476 URL: https://issues.apache.org/jira/browse/HIVE-5476 Project: Hive Issue Type: Bug Reporter: Thejas M Nair As seen in 0.12 build with hadoop1 - https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ Following tests fail - >>> org.apache.hadoop.hive.ql.security.TestMetastoreAuthorizationProvider.testSimplePrivileges >>> 12 sec 1 >>> org.apache.hadoop.hive.ql.security.TestStorageBasedClientSideAuthorizationProvider.testSimplePrivileges >>> 12 sec 1 >>> org.apache.hadoop.hive.ql.security.TestStorageBasedMetastoreAuthorizationProvider.testSimplePrivileges >>> 12 sec 1 > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5475) TestStatsPublisherEnhanced tests fail in sequential test run
[ https://issues.apache.org/jira/browse/HIVE-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thejas M Nair updated HIVE-5475: Description: As seen in 0.12 build with hadoop1 - https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ Following tests fail - >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherOneStat >>> 1.5 sec 1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisher >>> 0.84 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdates >>> 0.99 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdatesSubsetStatistics >>> 0.93 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsAggregatorCleanUp was: As seen in https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ Following tests fail - >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherOneStat >>> 1.5 sec 1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisher >>> 0.84 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdates >>> 0.99 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdatesSubsetStatistics >>> 0.93 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsAggregatorCleanUp > TestStatsPublisherEnhanced tests fail in sequential test run > > > Key: HIVE-5475 > URL: https://issues.apache.org/jira/browse/HIVE-5475 > Project: Hive > Issue Type: Bug >Reporter: Thejas M Nair > > As seen in 0.12 build with hadoop1 - > https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ > Following tests fail - > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherOneStat > >>>1.5 sec 1 > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisher > >>> 0.84 sec1 > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdates > >>>0.99 sec1 > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdatesSubsetStatistics > >>>0.93 sec1 > >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsAggregatorCleanUp -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5475) TestStatsPublisherEnhanced tests fail in sequential test run
[
https://issues.apache.org/jira/browse/HIVE-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787790#comment-13787790
]
Thejas M Nair commented on HIVE-5475:
-
{code}
Stacktrace
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at
org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.tearDown(TestStatsPublisherEnhanced.java:61)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:422)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:931)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:785)
{code}
> TestStatsPublisherEnhanced tests fail in sequential test run
>
>
> Key: HIVE-5475
> URL: https://issues.apache.org/jira/browse/HIVE-5475
> Project: Hive
> Issue Type: Bug
>Reporter: Thejas M Nair
>
> As seen in 0.12 build with hadoop1 -
> https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/
> Following tests fail -
> >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherOneStat
> >>>1.5 sec 1
> >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisher
> >>> 0.84 sec1
> >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdates
> >>>0.99 sec1
> >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdatesSubsetStatistics
> >>>0.93 sec1
> >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsAggregatorCleanUp
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (HIVE-5475) TestStatsPublisherEnhanced tests fail in sequential test run
Thejas M Nair created HIVE-5475: --- Summary: TestStatsPublisherEnhanced tests fail in sequential test run Key: HIVE-5475 URL: https://issues.apache.org/jira/browse/HIVE-5475 Project: Hive Issue Type: Bug Reporter: Thejas M Nair As seen in https://builds.apache.org/job/Hive-branch-0.12-hadoop1/lastCompletedBuild/testReport/ Following tests fail - >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherOneStat >>> 1.5 sec 1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisher >>> 0.84 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdates >>> 0.99 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsPublisherMultipleUpdatesSubsetStatistics >>> 0.93 sec1 >>> org.apache.hadoop.hive.ql.exec.TestStatsPublisherEnhanced.testStatsAggregatorCleanUp -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5474) TestThriftHttpCLIService.testExecuteStatement fails in sequential run
Thejas M Nair created HIVE-5474: --- Summary: TestThriftHttpCLIService.testExecuteStatement fails in sequential run Key: HIVE-5474 URL: https://issues.apache.org/jira/browse/HIVE-5474 Project: Hive Issue Type: Bug Components: HiveServer2 Reporter: Thejas M Nair Assignee: Vaibhav Gumashta This is seen in hive 0.12 branch sequential test run. TestThriftHttpCLIService.testExecuteStatement https://builds.apache.org/job/Hive-branch-0.12-hadoop1/13/testReport/org.apache.hive.service.cli.thrift/TestThriftHttpCLIService/testExecuteStatement/ stderr has "FAILED: Error in acquiring locks: Locks on the underlying objects cannot be acquired. retry after some time" -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5454) HCatalog runs a partition listing with an empty filter
[
https://issues.apache.org/jira/browse/HIVE-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787751#comment-13787751
]
Harsh J commented on HIVE-5454:
---
Looked into the single test failure and the test seems unrelated to my changes.
Oddly
https://builds.apache.org/job/PreCommit-HIVE-Build/1061/testReport/org.apache.hive.hcatalog.listener/TestNotificationListener/
reports the test passed.
> HCatalog runs a partition listing with an empty filter
> --
>
> Key: HIVE-5454
> URL: https://issues.apache.org/jira/browse/HIVE-5454
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 0.12.0
>Reporter: Harsh J
> Attachments: D13317.1.patch, D13317.2.patch, D13317.3.patch
>
>
> This is a HCATALOG-527 caused regression, wherein the HCatLoader's way of
> calling HCatInputFormat causes it to do 2x partition lookups - once without
> the filter, and then again with the filter.
> For tables with large number partitions (10, say), the non-filter lookup
> proves fatal both to the client ("Read timed out" errors from
> ThriftMetaStoreClient cause the server doesn't respond) and to the server
> (too much data loaded into the cache, OOME, or slowdown).
> The fix would be to use a single call that also passes a partition filter
> information, as was in the case of HCatalog 0.4 sources before HCATALOG-527.
> (HCatalog-release-wise, this affects all 0.5.x users)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5454) HCatalog runs a partition listing with an empty filter
[
https://issues.apache.org/jira/browse/HIVE-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787747#comment-13787747
]
Hive QA commented on HIVE-5454:
---
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12607088/D13317.3.patch
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 4059 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.listener.TestNotificationListener.testAMQListener
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1061/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1061/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
> HCatalog runs a partition listing with an empty filter
> --
>
> Key: HIVE-5454
> URL: https://issues.apache.org/jira/browse/HIVE-5454
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 0.12.0
>Reporter: Harsh J
> Attachments: D13317.1.patch, D13317.2.patch, D13317.3.patch
>
>
> This is a HCATALOG-527 caused regression, wherein the HCatLoader's way of
> calling HCatInputFormat causes it to do 2x partition lookups - once without
> the filter, and then again with the filter.
> For tables with large number partitions (10, say), the non-filter lookup
> proves fatal both to the client ("Read timed out" errors from
> ThriftMetaStoreClient cause the server doesn't respond) and to the server
> (too much data loaded into the cache, OOME, or slowdown).
> The fix would be to use a single call that also passes a partition filter
> information, as was in the case of HCatalog 0.4 sources before HCATALOG-527.
> (HCatalog-release-wise, this affects all 0.5.x users)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5423) Speed up testing of scalar UDFS
[ https://issues.apache.org/jira/browse/HIVE-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787737#comment-13787737 ] Edward Capriolo commented on HIVE-5423: --- Ok looks good! yay! > Speed up testing of scalar UDFS > --- > > Key: HIVE-5423 > URL: https://issues.apache.org/jira/browse/HIVE-5423 > Project: Hive > Issue Type: Improvement >Reporter: Edward Capriolo >Assignee: Edward Capriolo > Attachments: HIVE-5423.1.patch.txt, HIVE-5423.5.patch.txt, > HIVE-5423.6.patch.txt, HIVE-5423.patch.txt > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5372) Refactor TypeInfo and PrimitiveTypeEntry class hierachy to eliminate info repetition
[ https://issues.apache.org/jira/browse/HIVE-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787722#comment-13787722 ] Ashutosh Chauhan commented on HIVE-5372: +1 > Refactor TypeInfo and PrimitiveTypeEntry class hierachy to eliminate info > repetition > > > Key: HIVE-5372 > URL: https://issues.apache.org/jira/browse/HIVE-5372 > Project: Hive > Issue Type: Improvement > Components: Types >Affects Versions: 0.12.0 >Reporter: Xuefu Zhang >Assignee: Xuefu Zhang > Fix For: 0.13.0 > > Attachments: HIVE-5372.1.patch, HIVE-5372.2.patch, HIVE-5372.3.patch, > HIVE-5372.4.patch, HIVE-5372.patch > > > TypeInfo with its sub-classes and PrimititiveTypeEntry class seem having > repetitive information, such as type names and type params. It will be good > if we can streamline the information organization. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5473) sqrt of -ve value returns null instead of throwing an error
N Campbell created HIVE-5473: Summary: sqrt of -ve value returns null instead of throwing an error Key: HIVE-5473 URL: https://issues.apache.org/jira/browse/HIVE-5473 Project: Hive Issue Type: Bug Affects Versions: 0.11.0 Reporter: N Campbell Priority: Minor select sqrt( -4 ) from t will return a null instead of throwing an exception. no discussion on web page that this would be by design to not throw an error. https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-DateFunctions -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-3183) case expression should allow different types per ISO-SQL 2011
[ https://issues.apache.org/jira/browse/HIVE-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787715#comment-13787715 ] N Campbell commented on HIVE-3183: -- I am not planning to commit code changes to Apache. I'll leave that to Cloudera, Hortonworks and others who are incrementally improving Hive-QL :-) The intent is to enable others in the public domain to understand the bugs and opportunities that exist re Hive-QL types and SQL support distinct from working within the the supplied grammar or hand writing work arounds etc > case expression should allow different types per ISO-SQL 2011 > - > > Key: HIVE-3183 > URL: https://issues.apache.org/jira/browse/HIVE-3183 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.8.0 >Reporter: N Campbell > Attachments: Hive-3183.patch.txt, udf_when_type_wrong2.q.out, > udf_when_type_wrong3.q.out > > > The ISO-SQL standard specification for CASE allows the specification to > include different types in the WHEN and ELSE blocks including this example > which mixes smallint and integer types > select case when vsint.csint is not null then vsint.csint else 1 end from > cert.vsint vsint > The Apache Hive docs do not state how it deviates from the standard or any > given restrictions so unsure if this is a bug vs an enhancement. Many SQL > applications mix so this seems to be a restrictive implementation if this is > by design. > Argument type mismatch '1': The expression after ELSE should have the same > type as those after THEN: "smallint" is expected but "int" is found -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-3183) case expression should allow different types per ISO-SQL 2011
[ https://issues.apache.org/jira/browse/HIVE-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787714#comment-13787714 ] Ashutosh Chauhan commented on HIVE-3183: Would you like to format this as a patch and submit for review? > case expression should allow different types per ISO-SQL 2011 > - > > Key: HIVE-3183 > URL: https://issues.apache.org/jira/browse/HIVE-3183 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.8.0 >Reporter: N Campbell > Attachments: Hive-3183.patch.txt, udf_when_type_wrong2.q.out, > udf_when_type_wrong3.q.out > > > The ISO-SQL standard specification for CASE allows the specification to > include different types in the WHEN and ELSE blocks including this example > which mixes smallint and integer types > select case when vsint.csint is not null then vsint.csint else 1 end from > cert.vsint vsint > The Apache Hive docs do not state how it deviates from the standard or any > given restrictions so unsure if this is a bug vs an enhancement. Many SQL > applications mix so this seems to be a restrictive implementation if this is > by design. > Argument type mismatch '1': The expression after ELSE should have the same > type as those after THEN: "smallint" is expected but "int" is found -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5472) support a simple scalar which returns the current timestamp
N Campbell created HIVE-5472: Summary: support a simple scalar which returns the current timestamp Key: HIVE-5472 URL: https://issues.apache.org/jira/browse/HIVE-5472 Project: Hive Issue Type: Improvement Affects Versions: 0.11.0 Reporter: N Campbell ISO-SQL has two forms of functions local and current timestamp where the former is a TIMESTAMP WITHOUT TIMEZONE and the latter with TIME ZONE select cast ( unix_timestamp() as timestamp ) from T implement a function which computes LOCAL TIMESTAMP which would be the current timestamp for the users session time zone. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5431) PassthroughOutputFormat SH changes causes IllegalArgumentException
[
https://issues.apache.org/jira/browse/HIVE-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787713#comment-13787713
]
Sushanth Sowmyan commented on HIVE-5431:
Thanks, guys. I'll open up a new jira for the tests for this.
> PassthroughOutputFormat SH changes causes IllegalArgumentException
> --
>
> Key: HIVE-5431
> URL: https://issues.apache.org/jira/browse/HIVE-5431
> Project: Hive
> Issue Type: Bug
>Affects Versions: 0.12.0
>Reporter: Sushanth Sowmyan
>Assignee: Sushanth Sowmyan
>Priority: Blocker
> Fix For: 0.12.0
>
> Attachments: HIVE-5431.2.patch, HIVE-5431.patch
>
>
> The recent changes with HIVE-4331 introduced a new key
> "hive.passthrough.storagehandler.of", whose value is set only on storage
> handler writes, but obviously, will not be set on reads. However,
> PlanUtils.configureJobPropertiesForStorageHandler winds up trying to set the
> key for both cases into jobProperties, which cause any reads that are not
> preceeded by writes to fail.
> Basically, if you have a .q in which you insert data into a hbase table and
> then read it, it's okay. If you have a .q in which you only read data, it
> throws an IllegalArgumentException, like so:
> {noformat}
> 2013-09-30 16:20:01,989 ERROR CliDriver (SessionState.java:printError(419)) -
> Failed with exception java.io.IOException:java.lang.IllegalArgumentException:
> Property value must not be null
> java.io.IOException: java.lang.IllegalArgumentException: Property value must
> not be null
> at
> org.apache.hadoop.hive.ql.exec.FetchOperator.getNextRow(FetchOperator.java:551)
> at
> org.apache.hadoop.hive.ql.exec.FetchOperator.pushRow(FetchOperator.java:489)
> at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(FetchTask.java:136)
> at org.apache.hadoop.hive.ql.Driver.getResults(Driver.java:1471)
> at
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:271)
> at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:216)
> at
> org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:413)
> at
> org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:348)
> at
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:446)
> at
> org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:456)
> at
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:737)
> at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:675)
> at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:614)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
> Caused by: java.lang.IllegalArgumentException: Property value must not be null
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:88)
> at org.apache.hadoop.conf.Configuration.set(Configuration.java:810)
> at org.apache.hadoop.conf.Configuration.set(Configuration.java:792)
> at
> org.apache.hadoop.hive.ql.exec.Utilities.copyTableJobPropertiesToConf(Utilities.java:1826)
> at
> org.apache.hadoop.hive.ql.exec.FetchOperator.getRecordReader(FetchOperator.java:380)
> at
> org.apache.hadoop.hive.ql.exec.FetchOperator.getNextRow(FetchOperator.java:515)
> ... 17 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-4388) HBase tests fail against Hadoop 2
[ https://issues.apache.org/jira/browse/HIVE-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787712#comment-13787712 ] Sushanth Sowmyan commented on HIVE-4388: Well, as of right now, 0.12 should work fine with 0.96 without this patch on hadoop 1.x. The current plan is to commit this patch on hive trunk, which would be 0.13. I have one more task (tests for HIVE-5431) and then will get back to getting this patch in. > HBase tests fail against Hadoop 2 > - > > Key: HIVE-4388 > URL: https://issues.apache.org/jira/browse/HIVE-4388 > Project: Hive > Issue Type: Bug > Components: HBase Handler >Reporter: Gunther Hagleitner >Assignee: Brock Noland > Attachments: HIVE-4388.patch, HIVE-4388.patch, HIVE-4388.patch, > HIVE-4388.patch, HIVE-4388.patch, HIVE-4388.patch, HIVE-4388.patch, > HIVE-4388.patch, HIVE-4388-wip.txt > > > Currently we're building by default against 0.92. When you run against hadoop > 2 (-Dhadoop.mr.rev=23) builds fail because of: HBASE-5963. > HIVE-3861 upgrades the version of hbase used. This will get you past the > problem in HBASE-5963 (which was fixed in 0.94.1) but fails with: HBASE-6396. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5471) allow timestamp literal per ISO-SQL
N Campbell created HIVE-5471:
Summary: allow timestamp literal per ISO-SQL
Key: HIVE-5471
URL: https://issues.apache.org/jira/browse/HIVE-5471
Project: Hive
Issue Type: Improvement
Affects Versions: 0.11.0
Reporter: N Campbell
Support the ISO-SQL timestamp literal specification
select timestamp '1999-01-01 12:23.30.01' from tversion
instead of having to use
select cast('1999-01-01 12:23:30.01' as timestamp) from tversion
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (HIVE-5470) support extract function
N Campbell created HIVE-5470: Summary: support extract function Key: HIVE-5470 URL: https://issues.apache.org/jira/browse/HIVE-5470 Project: Hive Issue Type: Improvement Affects Versions: 0.11.0 Reporter: N Campbell Priority: Minor You have the equivalent scalar functions but do not offer ISO-SQL extract which should be a small enhancement. Note, the second() scalar does not return the fractional seconds in a timestamp with ISO-SQL would expect extract (second) to implement. select extract (year from cts), vs select rnum, year (cts), month( cts), day( cts), hour(cts), minute (cts), second( cts), cts from tts -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-3184) remove existing restriction that union must be defined within a derived table (follow ISO-SQL 2011)
[ https://issues.apache.org/jira/browse/HIVE-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated HIVE-3184: - Summary: remove existing restriction that union must be defined within a derived table (follow ISO-SQL 2011) (was: remove existing restriction that union must be defined within a derived table (follow ISO-SQL 2012)) > remove existing restriction that union must be defined within a derived table > (follow ISO-SQL 2011) > --- > > Key: HIVE-3184 > URL: https://issues.apache.org/jira/browse/HIVE-3184 > Project: Hive > Issue Type: Improvement > Components: SQL >Affects Versions: 0.8.0 >Reporter: N Campbell > > Don't make SQL applications have to wrap the union operation within a derived > table per the SQL standard. Failing to do so results in Top level UNION is > not supported currently; use a subquery > i.e. > select c1, c2 from cert.tset1 tset1 union all select c1, c2 from cert.tset2 > tset2 > vs > select * from ( select c1, c2 from cert.tset1 tset1 union all select c1, c2 > from cert.tset2 tset2 ) T -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-3185) allow union set operation without ALL keyword (align to ISO-SQL 2011 specification)
[ https://issues.apache.org/jira/browse/HIVE-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated HIVE-3185: - Summary: allow union set operation without ALL keyword (align to ISO-SQL 2011 specification) (was: allow union set operation without ALL keyword (align to ISO-SQL 2012 specification)) > allow union set operation without ALL keyword (align to ISO-SQL 2011 > specification) > --- > > Key: HIVE-3185 > URL: https://issues.apache.org/jira/browse/HIVE-3185 > Project: Hive > Issue Type: Improvement > Components: SQL >Affects Versions: 0.8.0 >Reporter: N Campbell > > Allow a union operation to be specified as union in addition to > th union all > Common requirement of queries to project two sets where it is not always the > case you want distinct rows in the set. Failing to do so obviously will > result in the current exception: > mismatched input 'select' expecting ALL near 'union' in query operator -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-3186) support having without a grouping operation (per ISO-SQL 2011)
[ https://issues.apache.org/jira/browse/HIVE-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated HIVE-3186: - Summary: support having without a grouping operation (per ISO-SQL 2011) (was: support having without a grouping operation (per ISO-SQL 2012)) > support having without a grouping operation (per ISO-SQL 2011) > -- > > Key: HIVE-3186 > URL: https://issues.apache.org/jira/browse/HIVE-3186 > Project: Hive > Issue Type: Improvement > Components: SQL >Affects Versions: 0.8.0 >Reporter: N Campbell > > select count(*) from cert.tset1 tset1 having count(*) > 2 > granted you can manually write a grouped derived table and filter etc but it > valid to define a having statement (implicit grouped table). > HAVING specified without GROUP BY -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-3190) allow INTEGER as a type name in a column/cast expression (per ISO-SQL 2011)
[
https://issues.apache.org/jira/browse/HIVE-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
N Campbell updated HIVE-3190:
-
Summary: allow INTEGER as a type name in a column/cast expression (per
ISO-SQL 2011) (was: allow INTEGER as a type name in a column/cast expression
(per ISO-SQL 2012))
> allow INTEGER as a type name in a column/cast expression (per ISO-SQL 2011)
> ---
>
> Key: HIVE-3190
> URL: https://issues.apache.org/jira/browse/HIVE-3190
> Project: Hive
> Issue Type: Improvement
> Components: SQL
>Affects Versions: 0.8.0
>Reporter: N Campbell
>
> Just extend the parser to allow INTEGER instead of making folks use INT
> select cast('10' as integer) from cert.tversion tversion
> FAILED: Parse Error: line 1:20 cannot recognize input near 'integer' ')'
> 'from' in primitive type specification
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-3183) case expression should allow different types per ISO-SQL 2011
[ https://issues.apache.org/jira/browse/HIVE-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated HIVE-3183: - Summary: case expression should allow different types per ISO-SQL 2011 (was: case expression should allow different types per ISO-SQL 2012) > case expression should allow different types per ISO-SQL 2011 > - > > Key: HIVE-3183 > URL: https://issues.apache.org/jira/browse/HIVE-3183 > Project: Hive > Issue Type: Bug > Components: SQL >Affects Versions: 0.8.0 >Reporter: N Campbell > Attachments: Hive-3183.patch.txt, udf_when_type_wrong2.q.out, > udf_when_type_wrong3.q.out > > > The ISO-SQL standard specification for CASE allows the specification to > include different types in the WHEN and ELSE blocks including this example > which mixes smallint and integer types > select case when vsint.csint is not null then vsint.csint else 1 end from > cert.vsint vsint > The Apache Hive docs do not state how it deviates from the standard or any > given restrictions so unsure if this is a bug vs an enhancement. Many SQL > applications mix so this seems to be a restrictive implementation if this is > by design. > Argument type mismatch '1': The expression after ELSE should have the same > type as those after THEN: "smallint" is expected but "int" is found -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-3188) allow cast to use double precision per ISO-SQL 2011
[
https://issues.apache.org/jira/browse/HIVE-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
N Campbell updated HIVE-3188:
-
Summary: allow cast to use double precision per ISO-SQL 2011 (was: allow
cast to use double precision per ISO-SQL 2012)
> allow cast to use double precision per ISO-SQL 2011
> ---
>
> Key: HIVE-3188
> URL: https://issues.apache.org/jira/browse/HIVE-3188
> Project: Hive
> Issue Type: Improvement
>Affects Versions: 0.8.0
>Reporter: N Campbell
>
> While ISO-SQL allows cast('10.3' as double precision) Hive forces you to say
> cast('10.3' as double ). Accept the additional keyword.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-3194) implement the JDBC canonical/ISO-SQL 2011 scalar functions
[ https://issues.apache.org/jira/browse/HIVE-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated HIVE-3194: - Summary: implement the JDBC canonical/ISO-SQL 2011 scalar functions (was: implement the JDBC canonical/ISO-SQL 2012 scalar functions) > implement the JDBC canonical/ISO-SQL 2011 scalar functions > -- > > Key: HIVE-3194 > URL: https://issues.apache.org/jira/browse/HIVE-3194 > Project: Hive > Issue Type: Improvement > Components: JDBC, SQL, UDF >Affects Versions: 0.8.0, 0.11.0 >Reporter: N Campbell > Attachments: Hive-3194.patch > > > The Hive driver does not return any canonical JDBC scalar functions (per JDBC > 3.0/4.0). Similarly, while Hive has various 'similar' scalar functions their > signature (name etc) is not the same as ISO-SQL equivalent. It would be > better for portable dynamic SQL applications to see more alignment by Hive > etc to both standards. In some cases it is small syntactic changes/tweaks > (i.e. see mod, substring etc). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5461) lag lead do not offer ISO-SQL 2011 null treatment
[ https://issues.apache.org/jira/browse/HIVE-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated HIVE-5461: - Summary: lag lead do not offer ISO-SQL 2011 null treatment (was: lag lead do not offer ISO-SQL 2012 null treatment ) > lag lead do not offer ISO-SQL 2011 null treatment > -- > > Key: HIVE-5461 > URL: https://issues.apache.org/jira/browse/HIVE-5461 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.11.0 >Reporter: N Campbell >Priority: Minor > > ISO-SQL lag and lead provide clauses that allow the author to denote how > nulls are treated (respect or ignore nulls). Hive does not. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5469) support nullif
N Campbell created HIVE-5469: Summary: support nullif Key: HIVE-5469 URL: https://issues.apache.org/jira/browse/HIVE-5469 Project: Hive Issue Type: Improvement Affects Versions: 0.11.0 Reporter: N Campbell Priority: Minor Have to express case expression to work around lack of NULLIF select nullif(cint, 1) from tint select cint, case when cint = 1 then null else cint end from tint -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5454) HCatalog runs a partition listing with an empty filter
[
https://issues.apache.org/jira/browse/HIVE-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-5454:
--
Attachment: D13317.3.patch
QwertyManiac updated the revision "HIVE-5454 [jira] HCatalog runs a partition
listing with an empty filter".
Fixed 4 reported checkstyle violations. Lint reported fine from arc, so
didn't notice these earlier.
Reviewers: JIRA
REVISION DETAIL
https://reviews.facebook.net/D13317
CHANGE SINCE LAST DIFF
https://reviews.facebook.net/D13317?vs=41043&id=41049#toc
AFFECTED FILES
hcatalog/core/src/main/java/org/apache/hive/hcatalog/data/transfer/impl/HCatInputFormatReader.java
hcatalog/core/src/main/java/org/apache/hive/hcatalog/mapreduce/HCatInputFormat.java
hcatalog/core/src/test/java/org/apache/hive/hcatalog/mapreduce/HCatMapReduceTest.java
hcatalog/hcatalog-pig-adapter/src/main/java/org/apache/hive/hcatalog/pig/HCatLoader.java
hcatalog/src/docs/src/documentation/content/xdocs/inputoutput.xml
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hcatalog/utils/HBaseReadWrite.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/GroupByAge.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/ReadJson.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/ReadRC.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/ReadText.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/ReadWrite.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/SimpleRead.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/StoreComplex.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/StoreDemo.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/StoreNumbers.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/SumNumbers.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/TypeDataCheck.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/WriteJson.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/WriteRC.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/WriteText.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/WriteTextPartitioned.java
hcatalog/storage-handlers/hbase/src/test/org/apache/hive/hcatalog/hbase/TestHBaseInputFormat.java
To: JIRA, QwertyManiac
> HCatalog runs a partition listing with an empty filter
> --
>
> Key: HIVE-5454
> URL: https://issues.apache.org/jira/browse/HIVE-5454
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 0.12.0
>Reporter: Harsh J
> Attachments: D13317.1.patch, D13317.2.patch, D13317.3.patch
>
>
> This is a HCATALOG-527 caused regression, wherein the HCatLoader's way of
> calling HCatInputFormat causes it to do 2x partition lookups - once without
> the filter, and then again with the filter.
> For tables with large number partitions (10, say), the non-filter lookup
> proves fatal both to the client ("Read timed out" errors from
> ThriftMetaStoreClient cause the server doesn't respond) and to the server
> (too much data loaded into the cache, OOME, or slowdown).
> The fix would be to use a single call that also passes a partition filter
> information, as was in the case of HCatalog 0.4 sources before HCATALOG-527.
> (HCatalog-release-wise, this affects all 0.5.x users)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5423) Speed up testing of scalar UDFS
[
https://issues.apache.org/jira/browse/HIVE-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787685#comment-13787685
]
Hive QA commented on HIVE-5423:
---
{color:red}Overall{color}: -1 at least one tests failed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12607080/HIVE-5423.6.patch.txt
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 4061 tests executed
*Failed tests:*
{noformat}
org.apache.hive.hcatalog.listener.TestNotificationListener.testAMQListener
{noformat}
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1060/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1060/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests failed with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
> Speed up testing of scalar UDFS
> ---
>
> Key: HIVE-5423
> URL: https://issues.apache.org/jira/browse/HIVE-5423
> Project: Hive
> Issue Type: Improvement
>Reporter: Edward Capriolo
>Assignee: Edward Capriolo
> Attachments: HIVE-5423.1.patch.txt, HIVE-5423.5.patch.txt,
> HIVE-5423.6.patch.txt, HIVE-5423.patch.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (HIVE-5468) allow null ordering to be defined on cursor specification
N Campbell created HIVE-5468: Summary: allow null ordering to be defined on cursor specification Key: HIVE-5468 URL: https://issues.apache.org/jira/browse/HIVE-5468 Project: Hive Issue Type: Improvement Affects Versions: 0.11.0 Reporter: N Campbell Similar comment to HIVE-5467 select rnum, c1, c2 from tset1 tset1 order by c1 nulls first, c2 nulls last -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5467) allow null ordering specification in a windowed aggregate
N Campbell created HIVE-5467: Summary: allow null ordering specification in a windowed aggregate Key: HIVE-5467 URL: https://issues.apache.org/jira/browse/HIVE-5467 Project: Hive Issue Type: Improvement Affects Versions: 0.11.0 Reporter: N Campbell A business user may require that nulls are sorted first with respect to an analytical expression as opposed to last. Hive does not support the null ordering specification. select rnum, c1, c2, c3, rank() over(order c1 desc nulls first ) from tolap order by rnum Error: Query returned non-zero code: 4, cause: FAILED: ParseException line 1:37 cannot recognize input near 'order' 'c1' 'desc' in order by clause You can fake is by ordering on a case expression select rnum, c1, c2, c3, rank() over(order by case when c1 is null then 0 else 1 end, c1 desc ) from tolap order by rnum -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
[ https://issues.apache.org/jira/browse/HIVE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] N Campbell updated HIVE-5460: - Description: ISO-SQL 2011 defines how lag and lead should behave when invalid offsets are provided to the functions. i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by tint.rnum) from tint tint Instead of a meaningful error (as other vendors will emit) you get Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask SQLState: 08S01 ErrorCode: 2 was: ISO-SQL 2012 defines how lag and lead should behave when invalid offsets are provided to the functions. i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by tint.rnum) from tint tint Instead of a meaningful error (as other vendors will emit) you get Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask SQLState: 08S01 ErrorCode: 2 > invalid offsets in lag lead should return an exception (per ISO-SQL) > - > > Key: HIVE-5460 > URL: https://issues.apache.org/jira/browse/HIVE-5460 > Project: Hive > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: N Campbell >Assignee: Edward Capriolo >Priority: Minor > > ISO-SQL 2011 defines how lag and lead should behave when invalid offsets are > provided to the functions. > i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by > tint.rnum) from tint tint > Instead of a meaningful error (as other vendors will emit) you get > Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, > return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask > SQLState: 08S01 > ErrorCode: 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5250) Specify UDF and other code from CLI
[ https://issues.apache.org/jira/browse/HIVE-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787672#comment-13787672 ] Hudson commented on HIVE-5250: -- FAILURE: Integrated in Hive-trunk-h0.21 #2383 (See [https://builds.apache.org/job/Hive-trunk-h0.21/2383/]) HIVE-5250 Allow admins to enable and disable non query commands (Brock Noland via egc) (ecapriolo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1529558) * /hive/trunk/cli/src/java/org/apache/hadoop/hive/cli/CliDriver.java * /hive/trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java * /hive/trunk/conf/hive-default.xml.template * /hive/trunk/hwi/src/java/org/apache/hadoop/hive/hwi/HWISessionItem.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/processors/CommandProcessorFactory.java * /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/processors/HiveCommand.java * /hive/trunk/ql/src/test/org/apache/hadoop/hive/ql/processors * /hive/trunk/ql/src/test/org/apache/hadoop/hive/ql/processors/TestCommandProcessorFactory.java * /hive/trunk/service/src/java/org/apache/hive/service/cli/operation/AddResourceOperation.java * /hive/trunk/service/src/java/org/apache/hive/service/cli/operation/DeleteResourceOperation.java * /hive/trunk/service/src/java/org/apache/hive/service/cli/operation/DfsOperation.java * /hive/trunk/service/src/java/org/apache/hive/service/cli/operation/ExecuteStatementOperation.java * /hive/trunk/service/src/java/org/apache/hive/service/cli/operation/HiveCommandOperation.java * /hive/trunk/service/src/java/org/apache/hive/service/cli/operation/OperationManager.java * /hive/trunk/service/src/java/org/apache/hive/service/cli/operation/SetOperation.java > Specify UDF and other code from CLI > --- > > Key: HIVE-5250 > URL: https://issues.apache.org/jira/browse/HIVE-5250 > Project: Hive > Issue Type: New Feature >Reporter: Edward Capriolo >Assignee: Edward Capriolo > > Because there are many dynamic languages for Java we no longer need to build > UDFs and other components statically. Instead we can build them at runtime. > This would create a new and exciting ad hoc way to work with hive. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
[ https://issues.apache.org/jira/browse/HIVE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787673#comment-13787673 ] N Campbell commented on HIVE-5460: -- You would need to go to the ISO web site http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=53681 > invalid offsets in lag lead should return an exception (per ISO-SQL) > - > > Key: HIVE-5460 > URL: https://issues.apache.org/jira/browse/HIVE-5460 > Project: Hive > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: N Campbell >Assignee: Edward Capriolo >Priority: Minor > > ISO-SQL 2012 defines how lag and lead should behave when invalid offsets are > provided to the functions. > i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by > tint.rnum) from tint tint > Instead of a meaningful error (as other vendors will emit) you get > Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, > return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask > SQLState: 08S01 > ErrorCode: 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
[ https://issues.apache.org/jira/browse/HIVE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787665#comment-13787665 ] Edward Capriolo commented on HIVE-5460: --- Can you provide a link to the definition of what it should do? > invalid offsets in lag lead should return an exception (per ISO-SQL) > - > > Key: HIVE-5460 > URL: https://issues.apache.org/jira/browse/HIVE-5460 > Project: Hive > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: N Campbell >Assignee: Edward Capriolo >Priority: Minor > > ISO-SQL 2012 defines how lag and lead should behave when invalid offsets are > provided to the functions. > i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by > tint.rnum) from tint tint > Instead of a meaningful error (as other vendors will emit) you get > Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, > return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask > SQLState: 08S01 > ErrorCode: 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Assigned] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
[ https://issues.apache.org/jira/browse/HIVE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo reassigned HIVE-5460: - Assignee: Edward Capriolo > invalid offsets in lag lead should return an exception (per ISO-SQL) > - > > Key: HIVE-5460 > URL: https://issues.apache.org/jira/browse/HIVE-5460 > Project: Hive > Issue Type: Bug >Affects Versions: 0.11.0 >Reporter: N Campbell >Assignee: Edward Capriolo >Priority: Minor > > ISO-SQL 2012 defines how lag and lead should behave when invalid offsets are > provided to the functions. > i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by > tint.rnum) from tint tint > Instead of a meaningful error (as other vendors will emit) you get > Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, > return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask > SQLState: 08S01 > ErrorCode: 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5464) allow OR conditions in table join
[ https://issues.apache.org/jira/browse/HIVE-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787652#comment-13787652 ] Edward Capriolo commented on HIVE-5464: --- Hive only supports equi-joins like this. You can still accomplish this query using a cart-product. Map Reduce can not easily make this query efficient, are you planning to work on this? We have to think carefully if we want this. There is a big danger in adding things to hive that can not be done efficiently in map/reduce. > allow OR conditions in table join > - > > Key: HIVE-5464 > URL: https://issues.apache.org/jira/browse/HIVE-5464 > Project: Hive > Issue Type: Improvement >Affects Versions: 0.11.0 >Reporter: N Campbell > > select tjoin1.c1, tjoin1.c2, tjoin2.c2 as c2j2 from tjoin1 tjoin1 inner join > tjoin2 tjoin2 on ( tjoin1.c1 = 10 or tjoin1.c1=20 ) > Query returned non-zero code: 10019, cause: FAILED: SemanticException [Error > 10019]: Line 1:96 OR not supported in JOIN currently '20' -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-5423) Speed up testing of scalar UDFS
[ https://issues.apache.org/jira/browse/HIVE-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Capriolo updated HIVE-5423: -- Attachment: HIVE-5423.6.patch.txt Renamed base class so hopefully we can keep it abstract. > Speed up testing of scalar UDFS > --- > > Key: HIVE-5423 > URL: https://issues.apache.org/jira/browse/HIVE-5423 > Project: Hive > Issue Type: Improvement >Reporter: Edward Capriolo >Assignee: Edward Capriolo > Attachments: HIVE-5423.1.patch.txt, HIVE-5423.5.patch.txt, > HIVE-5423.6.patch.txt, HIVE-5423.patch.txt > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5423) Speed up testing of scalar UDFS
[ https://issues.apache.org/jira/browse/HIVE-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787634#comment-13787634 ] Edward Capriolo commented on HIVE-5423: --- It seems like our tests/ junit cant understand not to run the bast class. I will rename it from TestBase to BaseTest and we will see if jenkins is happier > Speed up testing of scalar UDFS > --- > > Key: HIVE-5423 > URL: https://issues.apache.org/jira/browse/HIVE-5423 > Project: Hive > Issue Type: Improvement >Reporter: Edward Capriolo >Assignee: Edward Capriolo > Attachments: HIVE-5423.1.patch.txt, HIVE-5423.5.patch.txt, > HIVE-5423.patch.txt > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5466) add support for table and row constructors in a statement
N Campbell created HIVE-5466: Summary: add support for table and row constructors in a statement Key: HIVE-5466 URL: https://issues.apache.org/jira/browse/HIVE-5466 Project: Hive Issue Type: Improvement Reporter: N Campbell Priority: Minor Various filtering requirements can be expressed and performed more efficiently when row and table constructors can be pushed into a statement where (c1, c2 ) .. ( z1, z2) select t1.c1, t1.c2 from (values (10,'BB')) t1(c1,c2) etc -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5465) unable to express nested join
N Campbell created HIVE-5465: Summary: unable to express nested join Key: HIVE-5465 URL: https://issues.apache.org/jira/browse/HIVE-5465 Project: Hive Issue Type: Bug Affects Versions: 0.11.0 Reporter: N Campbell select tjoin2.rnum, tjoin1.c1, tjoin1.c2, tjoin2.c2 as c2j2, tjoin3.c2 as c2j3,tjoin4.c2 as c2j4 from (tjoin1 tjoin1 right outer join (tjoin2 tjoin2 left outer join tjoin3 tjoin3 on tjoin2.c1=tjoin3.c1) on (tjoin1.c1=tjoin2.c1)) left outer join tjoin4 tjoin4 on (tjoin1.c1=tjoin4.c1) Query returned non-zero code: 4, cause: FAILED: ParseException line 1:104 cannot recognize input near 'tjoin1' 'tjoin1' 'right' in subquery source -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5464) allow OR conditions in table join
N Campbell created HIVE-5464: Summary: allow OR conditions in table join Key: HIVE-5464 URL: https://issues.apache.org/jira/browse/HIVE-5464 Project: Hive Issue Type: Improvement Affects Versions: 0.11.0 Reporter: N Campbell select tjoin1.c1, tjoin1.c2, tjoin2.c2 as c2j2 from tjoin1 tjoin1 inner join tjoin2 tjoin2 on ( tjoin1.c1 = 10 or tjoin1.c1=20 ) Query returned non-zero code: 10019, cause: FAILED: SemanticException [Error 10019]: Line 1:96 OR not supported in JOIN currently '20' -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5463) support hypothetical ranking aggregates
N Campbell created HIVE-5463: Summary: support hypothetical ranking aggregates Key: HIVE-5463 URL: https://issues.apache.org/jira/browse/HIVE-5463 Project: Hive Issue Type: Improvement Affects Versions: 0.11.0 Reporter: N Campbell Priority: Minor existing function support does not include forms as select rank ( 5 ) within group ( order by vsint.csint ) from vsint vsint -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5462) improve error when an approximate numeric literal provided to lag lead
N Campbell created HIVE-5462: Summary: improve error when an approximate numeric literal provided to lag lead Key: HIVE-5462 URL: https://issues.apache.org/jira/browse/HIVE-5462 Project: Hive Issue Type: Bug Affects Versions: 0.11.0 Reporter: N Campbell Priority: Minor ISO SQL would define this as an error. select vint.rnum,vint.cint, lead( vint.cint, 1.70 ) over ( order by vint.rnum) from vint vint The issue is the error message returned by Hive Query returned non-zero code: 4, cause: FAILED: SemanticException Failed to breakup Windowing invocations into Groups. At least 1 group must only depend on input columns. Also check for circular dependencies. Underlying error: org.apache.hadoop.hive.ql.exec.UDFArgumentTypeException: Lead amount must be a integer value double was passed as parameter 1. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5461) lag lead do not offer ISO-SQL 2012 null treatment
N Campbell created HIVE-5461: Summary: lag lead do not offer ISO-SQL 2012 null treatment Key: HIVE-5461 URL: https://issues.apache.org/jira/browse/HIVE-5461 Project: Hive Issue Type: Improvement Affects Versions: 0.11.0 Reporter: N Campbell Priority: Minor ISO-SQL lag and lead provide clauses that allow the author to denote how nulls are treated (respect or ignore nulls). Hive does not. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (HIVE-5460) invalid offsets in lag lead should return an exception (per ISO-SQL)
N Campbell created HIVE-5460: Summary: invalid offsets in lag lead should return an exception (per ISO-SQL) Key: HIVE-5460 URL: https://issues.apache.org/jira/browse/HIVE-5460 Project: Hive Issue Type: Bug Affects Versions: 0.11.0 Reporter: N Campbell Priority: Minor ISO-SQL 2012 defines how lag and lead should behave when invalid offsets are provided to the functions. i.e. select tint.rnum,tint.cint, lag( tint.cint, -100 ) over ( order by tint.rnum) from tint tint Instead of a meaningful error (as other vendors will emit) you get Error: Query returned non-zero code: 2, cause: FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask SQLState: 08S01 ErrorCode: 2 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5431) PassthroughOutputFormat SH changes causes IllegalArgumentException
[
https://issues.apache.org/jira/browse/HIVE-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787585#comment-13787585
]
Hudson commented on HIVE-5431:
--
ABORTED: Integrated in Hive-branch-0.12-hadoop1 #14 (See
[https://builds.apache.org/job/Hive-branch-0.12-hadoop1/14/])
HIVE-5431 : PassthroughOutputFormat SH changes causes IllegalArgumentException
(Sushanth Sowmyan via Ashutosh Chauhan) (thejas:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1529499)
*
/hive/branches/branch-0.12/ql/src/java/org/apache/hadoop/hive/ql/plan/PlanUtils.java
> PassthroughOutputFormat SH changes causes IllegalArgumentException
> --
>
> Key: HIVE-5431
> URL: https://issues.apache.org/jira/browse/HIVE-5431
> Project: Hive
> Issue Type: Bug
>Affects Versions: 0.12.0
>Reporter: Sushanth Sowmyan
>Assignee: Sushanth Sowmyan
>Priority: Blocker
> Fix For: 0.12.0
>
> Attachments: HIVE-5431.2.patch, HIVE-5431.patch
>
>
> The recent changes with HIVE-4331 introduced a new key
> "hive.passthrough.storagehandler.of", whose value is set only on storage
> handler writes, but obviously, will not be set on reads. However,
> PlanUtils.configureJobPropertiesForStorageHandler winds up trying to set the
> key for both cases into jobProperties, which cause any reads that are not
> preceeded by writes to fail.
> Basically, if you have a .q in which you insert data into a hbase table and
> then read it, it's okay. If you have a .q in which you only read data, it
> throws an IllegalArgumentException, like so:
> {noformat}
> 2013-09-30 16:20:01,989 ERROR CliDriver (SessionState.java:printError(419)) -
> Failed with exception java.io.IOException:java.lang.IllegalArgumentException:
> Property value must not be null
> java.io.IOException: java.lang.IllegalArgumentException: Property value must
> not be null
> at
> org.apache.hadoop.hive.ql.exec.FetchOperator.getNextRow(FetchOperator.java:551)
> at
> org.apache.hadoop.hive.ql.exec.FetchOperator.pushRow(FetchOperator.java:489)
> at org.apache.hadoop.hive.ql.exec.FetchTask.fetch(FetchTask.java:136)
> at org.apache.hadoop.hive.ql.Driver.getResults(Driver.java:1471)
> at
> org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:271)
> at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:216)
> at
> org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:413)
> at
> org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:348)
> at
> org.apache.hadoop.hive.cli.CliDriver.processReader(CliDriver.java:446)
> at
> org.apache.hadoop.hive.cli.CliDriver.processFile(CliDriver.java:456)
> at
> org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:737)
> at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:675)
> at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:614)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
> Caused by: java.lang.IllegalArgumentException: Property value must not be null
> at
> com.google.common.base.Preconditions.checkArgument(Preconditions.java:88)
> at org.apache.hadoop.conf.Configuration.set(Configuration.java:810)
> at org.apache.hadoop.conf.Configuration.set(Configuration.java:792)
> at
> org.apache.hadoop.hive.ql.exec.Utilities.copyTableJobPropertiesToConf(Utilities.java:1826)
> at
> org.apache.hadoop.hive.ql.exec.FetchOperator.getRecordReader(FetchOperator.java:380)
> at
> org.apache.hadoop.hive.ql.exec.FetchOperator.getNextRow(FetchOperator.java:515)
> ... 17 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5402) StorageBasedAuthorizationProvider is not correctly able to determine that it is running from client-side
[ https://issues.apache.org/jira/browse/HIVE-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787586#comment-13787586 ] Hudson commented on HIVE-5402: -- ABORTED: Integrated in Hive-branch-0.12-hadoop1 #14 (See [https://builds.apache.org/job/Hive-branch-0.12-hadoop1/14/]) HIVE-5402 : StorageBasedAuthorizationProvider is not correctly able to determine that it is running from client-side (Sushanth Sowmyan via Ashutosh Chauhan) (thejas: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1529500) * /hive/branches/branch-0.12/ql/src/java/org/apache/hadoop/hive/ql/security/authorization/StorageBasedAuthorizationProvider.java * /hive/branches/branch-0.12/ql/src/test/org/apache/hadoop/hive/ql/security/TestClientSideAuthorizationProvider.java * /hive/branches/branch-0.12/ql/src/test/org/apache/hadoop/hive/ql/security/TestDefaultHiveMetastoreAuthorizationProvider.java * /hive/branches/branch-0.12/ql/src/test/org/apache/hadoop/hive/ql/security/TestMetastoreAuthorizationProvider.java * /hive/branches/branch-0.12/ql/src/test/org/apache/hadoop/hive/ql/security/TestStorageBasedClientSideAuthorizationProvider.java * /hive/branches/branch-0.12/ql/src/test/org/apache/hadoop/hive/ql/security/TestStorageBasedMetastoreAuthorizationProvider.java > StorageBasedAuthorizationProvider is not correctly able to determine that it > is running from client-side > > > Key: HIVE-5402 > URL: https://issues.apache.org/jira/browse/HIVE-5402 > Project: Hive > Issue Type: Bug > Components: Authorization >Reporter: Sushanth Sowmyan >Assignee: Sushanth Sowmyan >Priority: Blocker > Fix For: 0.12.0 > > Attachments: HIVE-5402.2.patch, HIVE-5402.patch > > > HIVE-5048 tried to change the StorageBasedAuthorizationProvider (SBAP) so > that it could be run from the client side as well. > However, there is a bug that causes SBAP to incorrectly conclude that it's > running from the metastore-side when it's actually running from the > client-side that causes it to throw a IllegalStateException claiming the > warehouse variable isn't set. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-4446) [HCatalog] Documentation for HIVE-4442, HIVE-4443, HIVE-4444
[ https://issues.apache.org/jira/browse/HIVE-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787581#comment-13787581 ] Lefty Leverenz commented on HIVE-4446: -- Changes made, pending feedback from Daniel. See https://cwiki.apache.org/confluence/display/Hive/WebHCat+Reference -- Hive and Jobs resources, plus deprecation notices in Queue resources. > [HCatalog] Documentation for HIVE-4442, HIVE-4443, HIVE- > > > Key: HIVE-4446 > URL: https://issues.apache.org/jira/browse/HIVE-4446 > Project: Hive > Issue Type: Improvement > Components: HCatalog >Reporter: Daniel Dai >Assignee: Lefty Leverenz > Fix For: 0.12.0 > > Attachments: HIVE-4446-1.patch > > -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HIVE-5459) Add --version option to hive script
[
https://issues.apache.org/jira/browse/HIVE-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787556#comment-13787556
]
Hive QA commented on HIVE-5459:
---
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12607060/HIVE-5459.1.patch
{color:green}SUCCESS:{color} +1 4059 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1058/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1058/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
> Add --version option to hive script
> ---
>
> Key: HIVE-5459
> URL: https://issues.apache.org/jira/browse/HIVE-5459
> Project: Hive
> Issue Type: Bug
> Components: Diagnosability
>Affects Versions: 0.11.0, 0.12.0
>Reporter: Prasad Mujumdar
>Assignee: Prasad Mujumdar
> Attachments: HIVE-5459.1.patch, HIVE-5459.1.patch
>
>
> Hive jars already contain all the build information, similar to hadoop. This
> was added as part of HiveServer2 feature.
> We are still missing the command line wrapper to extract that information
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-5454) HCatalog runs a partition listing with an empty filter
[
https://issues.apache.org/jira/browse/HIVE-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-5454:
--
Attachment: D13317.2.patch
QwertyManiac updated the revision "HIVE-5454 [jira] HCatalog runs a partition
listing with an empty filter".
Removed usage of removed deprecated methods.
Reviewers: JIRA
REVISION DETAIL
https://reviews.facebook.net/D13317
CHANGE SINCE LAST DIFF
https://reviews.facebook.net/D13317?vs=41025&id=41043#toc
AFFECTED FILES
hcatalog/core/src/main/java/org/apache/hive/hcatalog/data/transfer/impl/HCatInputFormatReader.java
hcatalog/core/src/main/java/org/apache/hive/hcatalog/mapreduce/HCatInputFormat.java
hcatalog/core/src/test/java/org/apache/hive/hcatalog/mapreduce/HCatMapReduceTest.java
hcatalog/hcatalog-pig-adapter/src/main/java/org/apache/hive/hcatalog/pig/HCatLoader.java
hcatalog/src/docs/src/documentation/content/xdocs/inputoutput.xml
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hcatalog/utils/HBaseReadWrite.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/GroupByAge.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/ReadJson.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/ReadRC.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/ReadText.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/ReadWrite.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/SimpleRead.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/StoreComplex.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/StoreDemo.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/StoreNumbers.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/SumNumbers.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/TypeDataCheck.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/WriteJson.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/WriteRC.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/WriteText.java
hcatalog/src/test/e2e/hcatalog/udfs/java/org/apache/hive/hcatalog/utils/WriteTextPartitioned.java
hcatalog/storage-handlers/hbase/src/test/org/apache/hive/hcatalog/hbase/TestHBaseInputFormat.java
To: JIRA, QwertyManiac
> HCatalog runs a partition listing with an empty filter
> --
>
> Key: HIVE-5454
> URL: https://issues.apache.org/jira/browse/HIVE-5454
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 0.12.0
>Reporter: Harsh J
> Attachments: D13317.1.patch, D13317.2.patch
>
>
> This is a HCATALOG-527 caused regression, wherein the HCatLoader's way of
> calling HCatInputFormat causes it to do 2x partition lookups - once without
> the filter, and then again with the filter.
> For tables with large number partitions (10, say), the non-filter lookup
> proves fatal both to the client ("Read timed out" errors from
> ThriftMetaStoreClient cause the server doesn't respond) and to the server
> (too much data loaded into the cache, OOME, or slowdown).
> The fix would be to use a single call that also passes a partition filter
> information, as was in the case of HCatalog 0.4 sources before HCATALOG-527.
> (HCatalog-release-wise, this affects all 0.5.x users)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5454) HCatalog runs a partition listing with an empty filter
[
https://issues.apache.org/jira/browse/HIVE-5454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787535#comment-13787535
]
Harsh J commented on HIVE-5454:
---
The removal of deprecated methods seems to have caught several usage of it
within hcatalog. I'll re-up a new patch that updates all old refs.
> HCatalog runs a partition listing with an empty filter
> --
>
> Key: HIVE-5454
> URL: https://issues.apache.org/jira/browse/HIVE-5454
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
>Affects Versions: 0.12.0
>Reporter: Harsh J
> Attachments: D13317.1.patch
>
>
> This is a HCATALOG-527 caused regression, wherein the HCatLoader's way of
> calling HCatInputFormat causes it to do 2x partition lookups - once without
> the filter, and then again with the filter.
> For tables with large number partitions (10, say), the non-filter lookup
> proves fatal both to the client ("Read timed out" errors from
> ThriftMetaStoreClient cause the server doesn't respond) and to the server
> (too much data loaded into the cache, OOME, or slowdown).
> The fix would be to use a single call that also passes a partition filter
> information, as was in the case of HCatalog 0.4 sources before HCATALOG-527.
> (HCatalog-release-wise, this affects all 0.5.x users)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HIVE-5372) Refactor TypeInfo and PrimitiveTypeEntry class hierachy to eliminate info repetition
[
https://issues.apache.org/jira/browse/HIVE-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787534#comment-13787534
]
Hive QA commented on HIVE-5372:
---
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12607054/HIVE-5372.4.patch
{color:green}SUCCESS:{color} +1 4059 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/1057/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/1057/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
> Refactor TypeInfo and PrimitiveTypeEntry class hierachy to eliminate info
> repetition
>
>
> Key: HIVE-5372
> URL: https://issues.apache.org/jira/browse/HIVE-5372
> Project: Hive
> Issue Type: Improvement
> Components: Types
>Affects Versions: 0.12.0
>Reporter: Xuefu Zhang
>Assignee: Xuefu Zhang
> Fix For: 0.13.0
>
> Attachments: HIVE-5372.1.patch, HIVE-5372.2.patch, HIVE-5372.3.patch,
> HIVE-5372.4.patch, HIVE-5372.patch
>
>
> TypeInfo with its sub-classes and PrimititiveTypeEntry class seem having
> repetitive information, such as type names and type params. It will be good
> if we can streamline the information organization.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-4898) make vectorized math functions work end-to-end (update VectorizationContext.java)
[ https://issues.apache.org/jira/browse/HIVE-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HIVE-4898: --- Status: Patch Available (was: Open) > make vectorized math functions work end-to-end (update > VectorizationContext.java) > - > > Key: HIVE-4898 > URL: https://issues.apache.org/jira/browse/HIVE-4898 > Project: Hive > Issue Type: Sub-task >Affects Versions: vectorization-branch >Reporter: Eric Hanson >Assignee: Eric Hanson > Attachments: HIVE-4898.3.patch > > > The vectorized math function VectorExpression classes were added in > HIVE-4822. This JIRA is to allow those to actually be used in a SQL query > end-to-end. This requires updating VectorizationContext to use the new > classes in vectorized expression creation. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (HIVE-4898) make vectorized math functions work end-to-end (update VectorizationContext.java)
[ https://issues.apache.org/jira/browse/HIVE-4898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jitendra Nath Pandey updated HIVE-4898: --- Status: Open (was: Patch Available) > make vectorized math functions work end-to-end (update > VectorizationContext.java) > - > > Key: HIVE-4898 > URL: https://issues.apache.org/jira/browse/HIVE-4898 > Project: Hive > Issue Type: Sub-task >Affects Versions: vectorization-branch >Reporter: Eric Hanson >Assignee: Eric Hanson > Attachments: HIVE-4898.3.patch > > > The vectorized math function VectorExpression classes were added in > HIVE-4822. This JIRA is to allow those to actually be used in a SQL query > end-to-end. This requires updating VectorizationContext to use the new > classes in vectorized expression creation. -- This message was sent by Atlassian JIRA (v6.1#6144)
