[jira] [Commented] (HIVE-7174) Do not accept string as scale and precision when reading Avro schema
[
https://issues.apache.org/jira/browse/HIVE-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026461#comment-14026461
]
Jarek Jarcec Cecho commented on HIVE-7174:
--
Thank you for bringing up this question [~leftylev]! I think that this
particular JIRA is just a bugfix that don't need explicit documentation. I've
however noticed that the linked wiki page do not contain any information about
decimal in Avro that was introduced in HIVE-5823, which is something that we
should rectify. I'm not sure how to proceed though - should I create a new doc
JIRA for that or do you want to reuse the existing HIVE-5823?
Do not accept string as scale and precision when reading Avro schema
Key: HIVE-7174
URL: https://issues.apache.org/jira/browse/HIVE-7174
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.14.0
Attachments: HIVE-7174.patch, dec.avro
I've noticed that the current AvroSerde will happily accept schema that uses
string instead of integer for scale and precision, e.g. fragment
{{precision:4,scale:1}} from following table:
{code}
CREATE TABLE `avro_dec1`(
`name` string COMMENT 'from deserializer',
`value` decimal(4,1) COMMENT 'from deserializer')
COMMENT 'just drop the schema right into the HQL'
ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
TBLPROPERTIES (
'numFiles'='1',
'avro.schema.literal'='{\namespace\:\com.howdy\,\name\:\some_schema\,\type\:\record\,\fields\:[{\name\:\name\,\type\:\string\},{\name\:\value\,\type\:{\type\:\bytes\,\logicalType\:\decimal\,\precision\:\4\,\scale\:\1\}}]}'
);
{code}
However the Decimal spec defined in AVRO-1402 requires only integer to be
there and hence is allowing only following fragment instead
{{precision:4,scale:1}} (e.g. no double quotes around numbers).
As Hive can propagate this incorrect schema to new files and hence creating
files with invalid schema, I think that we should alter the behavior and
insist on the correct schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-4064) Handle db qualified names consistently across all HiveQL statements
[ https://issues.apache.org/jira/browse/HIVE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026571#comment-14026571 ] Jarek Jarcec Cecho commented on HIVE-4064: -- You might need to set the status to Patch available if you want Hive committers to take a look [~caofangkun]. Handle db qualified names consistently across all HiveQL statements --- Key: HIVE-4064 URL: https://issues.apache.org/jira/browse/HIVE-4064 Project: Hive Issue Type: Bug Components: SQL Affects Versions: 0.10.0 Reporter: Shreepadma Venugopalan Assignee: caofangkun Attachments: HIVE-4064-1.patch Hive doesn't consistently handle db qualified names across all HiveQL statements. While some HiveQL statements such as SELECT support DB qualified names, other such as CREATE INDEX doesn't. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-7174) Do not accept string as scale and precision when reading Avro schema
[
https://issues.apache.org/jira/browse/HIVE-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027335#comment-14027335
]
Jarek Jarcec Cecho commented on HIVE-7174:
--
Cool, thank you [~leftylev]!
Do not accept string as scale and precision when reading Avro schema
Key: HIVE-7174
URL: https://issues.apache.org/jira/browse/HIVE-7174
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.14.0
Attachments: HIVE-7174.patch, dec.avro
I've noticed that the current AvroSerde will happily accept schema that uses
string instead of integer for scale and precision, e.g. fragment
{{precision:4,scale:1}} from following table:
{code}
CREATE TABLE `avro_dec1`(
`name` string COMMENT 'from deserializer',
`value` decimal(4,1) COMMENT 'from deserializer')
COMMENT 'just drop the schema right into the HQL'
ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
TBLPROPERTIES (
'numFiles'='1',
'avro.schema.literal'='{\namespace\:\com.howdy\,\name\:\some_schema\,\type\:\record\,\fields\:[{\name\:\name\,\type\:\string\},{\name\:\value\,\type\:{\type\:\bytes\,\logicalType\:\decimal\,\precision\:\4\,\scale\:\1\}}]}'
);
{code}
However the Decimal spec defined in AVRO-1402 requires only integer to be
there and hence is allowing only following fragment instead
{{precision:4,scale:1}} (e.g. no double quotes around numbers).
As Hive can propagate this incorrect schema to new files and hence creating
files with invalid schema, I think that we should alter the behavior and
insist on the correct schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-7174) Do not accept string as scale and precision when reading Avro schema
[
https://issues.apache.org/jira/browse/HIVE-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026028#comment-14026028
]
Jarek Jarcec Cecho commented on HIVE-7174:
--
Are you going to commit the changes [~xuefuz]?
Do not accept string as scale and precision when reading Avro schema
Key: HIVE-7174
URL: https://issues.apache.org/jira/browse/HIVE-7174
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.14.0
Attachments: HIVE-7174.patch, dec.avro
I've noticed that the current AvroSerde will happily accept schema that uses
string instead of integer for scale and precision, e.g. fragment
{{precision:4,scale:1}} from following table:
{code}
CREATE TABLE `avro_dec1`(
`name` string COMMENT 'from deserializer',
`value` decimal(4,1) COMMENT 'from deserializer')
COMMENT 'just drop the schema right into the HQL'
ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
TBLPROPERTIES (
'numFiles'='1',
'avro.schema.literal'='{\namespace\:\com.howdy\,\name\:\some_schema\,\type\:\record\,\fields\:[{\name\:\name\,\type\:\string\},{\name\:\value\,\type\:{\type\:\bytes\,\logicalType\:\decimal\,\precision\:\4\,\scale\:\1\}}]}'
);
{code}
However the Decimal spec defined in AVRO-1402 requires only integer to be
there and hence is allowing only following fragment instead
{{precision:4,scale:1}} (e.g. no double quotes around numbers).
As Hive can propagate this incorrect schema to new files and hence creating
files with invalid schema, I think that we should alter the behavior and
insist on the correct schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-7174) Do not accept string as scale and precision when reading Avro schema
[
https://issues.apache.org/jira/browse/HIVE-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-7174:
-
Attachment: dec.avro
Do not accept string as scale and precision when reading Avro schema
Key: HIVE-7174
URL: https://issues.apache.org/jira/browse/HIVE-7174
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.14.0
Attachments: HIVE-7174.patch, dec.avro
I've noticed that the current AvroSerde will happily accept schema that uses
string instead of integer for scale and precision, e.g. fragment
{{precision:4,scale:1}} from following table:
{code}
CREATE TABLE `avro_dec1`(
`name` string COMMENT 'from deserializer',
`value` decimal(4,1) COMMENT 'from deserializer')
COMMENT 'just drop the schema right into the HQL'
ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
TBLPROPERTIES (
'numFiles'='1',
'avro.schema.literal'='{\namespace\:\com.howdy\,\name\:\some_schema\,\type\:\record\,\fields\:[{\name\:\name\,\type\:\string\},{\name\:\value\,\type\:{\type\:\bytes\,\logicalType\:\decimal\,\precision\:\4\,\scale\:\1\}}]}'
);
{code}
However the Decimal spec defined in AVRO-1402 requires only integer to be
there and hence is allowing only following fragment instead
{{precision:4,scale:1}} (e.g. no double quotes around numbers).
As Hive can propagate this incorrect schema to new files and hence creating
files with invalid schema, I think that we should alter the behavior and
insist on the correct schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-7174) Do not accept string as scale and precision when reading Avro schema
[
https://issues.apache.org/jira/browse/HIVE-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14019542#comment-14019542
]
Jarek Jarcec Cecho commented on HIVE-7174:
--
I've noticed that file {{dev.avro}} has been created with incorrect schema, so
I've attached fixed version. Attached file should replace the one in
{{data/files/dec.avro}}.
Do not accept string as scale and precision when reading Avro schema
Key: HIVE-7174
URL: https://issues.apache.org/jira/browse/HIVE-7174
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.14.0
Attachments: HIVE-7174.patch, dec.avro
I've noticed that the current AvroSerde will happily accept schema that uses
string instead of integer for scale and precision, e.g. fragment
{{precision:4,scale:1}} from following table:
{code}
CREATE TABLE `avro_dec1`(
`name` string COMMENT 'from deserializer',
`value` decimal(4,1) COMMENT 'from deserializer')
COMMENT 'just drop the schema right into the HQL'
ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
TBLPROPERTIES (
'numFiles'='1',
'avro.schema.literal'='{\namespace\:\com.howdy\,\name\:\some_schema\,\type\:\record\,\fields\:[{\name\:\name\,\type\:\string\},{\name\:\value\,\type\:{\type\:\bytes\,\logicalType\:\decimal\,\precision\:\4\,\scale\:\1\}}]}'
);
{code}
However the Decimal spec defined in AVRO-1402 requires only integer to be
there and hence is allowing only following fragment instead
{{precision:4,scale:1}} (e.g. no double quotes around numbers).
As Hive can propagate this incorrect schema to new files and hence creating
files with invalid schema, I think that we should alter the behavior and
insist on the correct schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (HIVE-7174) Do not accept string as scale and precision when reading Avro schema
Jarek Jarcec Cecho created HIVE-7174:
Summary: Do not accept string as scale and precision when reading
Avro schema
Key: HIVE-7174
URL: https://issues.apache.org/jira/browse/HIVE-7174
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
I've noticed that the current AvroSerde will happily accept schema that uses
string instead of integer for scale and precision, e.g. fragment
{{precision:4,scale:1}} from following table:
{code}
CREATE TABLE `avro_dec1`(
`name` string COMMENT 'from deserializer',
`value` decimal(4,1) COMMENT 'from deserializer')
COMMENT 'just drop the schema right into the HQL'
ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
TBLPROPERTIES (
'numFiles'='1',
'avro.schema.literal'='{\namespace\:\com.howdy\,\name\:\some_schema\,\type\:\record\,\fields\:[{\name\:\name\,\type\:\string\},{\name\:\value\,\type\:{\type\:\bytes\,\logicalType\:\decimal\,\precision\:\4\,\scale\:\1\}}]}'
);
{code}
However the Decimal spec defined in AVRO-1402 requires only integer to be there
and hence is allowing only following fragment instead
{{precision:4,scale:1}} (e.g. no double quotes around numbers).
As Hive can propagate this incorrect schema to new files and hence creating
files with invalid schema, I think that we should alter the behavior and insist
on the correct schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-7174) Do not accept string as scale and precision when reading Avro schema
[
https://issues.apache.org/jira/browse/HIVE-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-7174:
-
Attachment: HIVE-7174.patch
Attaching patch that replaces method call {{getValueAsInt}} that is allowed to
do type transformations (String - Integer) with {{getIntValue}} that will fail
in case that user will use string instead. I've verified that Hive now do not
accepts the incorrect schema.
Do not accept string as scale and precision when reading Avro schema
Key: HIVE-7174
URL: https://issues.apache.org/jira/browse/HIVE-7174
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Attachments: HIVE-7174.patch
I've noticed that the current AvroSerde will happily accept schema that uses
string instead of integer for scale and precision, e.g. fragment
{{precision:4,scale:1}} from following table:
{code}
CREATE TABLE `avro_dec1`(
`name` string COMMENT 'from deserializer',
`value` decimal(4,1) COMMENT 'from deserializer')
COMMENT 'just drop the schema right into the HQL'
ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
TBLPROPERTIES (
'numFiles'='1',
'avro.schema.literal'='{\namespace\:\com.howdy\,\name\:\some_schema\,\type\:\record\,\fields\:[{\name\:\name\,\type\:\string\},{\name\:\value\,\type\:{\type\:\bytes\,\logicalType\:\decimal\,\precision\:\4\,\scale\:\1\}}]}'
);
{code}
However the Decimal spec defined in AVRO-1402 requires only integer to be
there and hence is allowing only following fragment instead
{{precision:4,scale:1}} (e.g. no double quotes around numbers).
As Hive can propagate this incorrect schema to new files and hence creating
files with invalid schema, I think that we should alter the behavior and
insist on the correct schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-7174) Do not accept string as scale and precision when reading Avro schema
[
https://issues.apache.org/jira/browse/HIVE-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-7174:
-
Fix Version/s: 0.14.0
Status: Patch Available (was: Open)
Do not accept string as scale and precision when reading Avro schema
Key: HIVE-7174
URL: https://issues.apache.org/jira/browse/HIVE-7174
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.14.0
Attachments: HIVE-7174.patch
I've noticed that the current AvroSerde will happily accept schema that uses
string instead of integer for scale and precision, e.g. fragment
{{precision:4,scale:1}} from following table:
{code}
CREATE TABLE `avro_dec1`(
`name` string COMMENT 'from deserializer',
`value` decimal(4,1) COMMENT 'from deserializer')
COMMENT 'just drop the schema right into the HQL'
ROW FORMAT SERDE
'org.apache.hadoop.hive.serde2.avro.AvroSerDe'
STORED AS INPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerInputFormat'
OUTPUTFORMAT
'org.apache.hadoop.hive.ql.io.avro.AvroContainerOutputFormat'
TBLPROPERTIES (
'numFiles'='1',
'avro.schema.literal'='{\namespace\:\com.howdy\,\name\:\some_schema\,\type\:\record\,\fields\:[{\name\:\name\,\type\:\string\},{\name\:\value\,\type\:{\type\:\bytes\,\logicalType\:\decimal\,\precision\:\4\,\scale\:\1\}}]}'
);
{code}
However the Decimal spec defined in AVRO-1402 requires only integer to be
there and hence is allowing only following fragment instead
{{precision:4,scale:1}} (e.g. no double quotes around numbers).
As Hive can propagate this incorrect schema to new files and hence creating
files with invalid schema, I think that we should alter the behavior and
insist on the correct schema.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Re: [ANNOUNCE] New Hive PMC Member - Xuefu Zhang
Wow, congratulations Xuefu! Excellent work! Jarcec On Fri, Feb 28, 2014 at 01:20:47AM -0800, Carl Steinbach wrote: I am pleased to announce that Xuefu Zhang has been elected to the Hive Project Management Committee. Please join me in congratulating Xuefu! Thanks. Carl signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive Committer - Remus Rusanu
Congratulations Remus, good work! Jarcec On Wed, Feb 26, 2014 at 08:58:43AM -0800, Carl Steinbach wrote: The Apache Hive PMC has voted to make Remus Rusanu a committer on the Apache Hive Project. Please join me in congratulating Remus! Thanks. Carl signature.asc Description: Digital signature
[jira] [Created] (HIVE-6394) Implement Timestmap in ParquetSerde
Jarek Jarcec Cecho created HIVE-6394: Summary: Implement Timestmap in ParquetSerde Key: HIVE-6394 URL: https://issues.apache.org/jira/browse/HIVE-6394 Project: Hive Issue Type: Bug Reporter: Jarek Jarcec Cecho This JIRA is to implement timestamp support in Parquet SerDe. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (HIVE-6394) Implement Timestmap in ParquetSerde
[ https://issues.apache.org/jira/browse/HIVE-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated HIVE-6394: - Issue Type: Sub-task (was: Bug) Parent: HIVE-6384 Implement Timestmap in ParquetSerde --- Key: HIVE-6394 URL: https://issues.apache.org/jira/browse/HIVE-6394 Project: Hive Issue Type: Sub-task Reporter: Jarek Jarcec Cecho This JIRA is to implement timestamp support in Parquet SerDe. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [ANNOUNCE] New Hive Committers - Sergey Shelukhin and Jason Dere
Congratulations Sergey and Jason, good job! Jarcec On Mon, Jan 27, 2014 at 08:36:37AM -0800, Carl Steinbach wrote: The Apache Hive PMC has voted to make Sergey Shelukhin and Jason Dere committers on the Apache Hive Project. Please join me in congratulating Sergey and Jason! Thanks. Carl signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive Committer - Vikram Dixit
Congratulations Vikram! Jarcec On Mon, Jan 06, 2014 at 08:58:06AM -0800, Carl Steinbach wrote: The Apache Hive PMC has voted to make Vikram Dixit a committer on the Apache Hive Project. Please join me in congratulating Vikram! Thanks. Carl signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive PMC Member - Gunther Hagleitner
Congratulations Gunther, good job! Jarcec On Thu, Dec 26, 2013 at 08:59:37PM -0800, Carl Steinbach wrote: I am pleased to announce that Gunther Hagleitner has been elected to the Hive Project Management Committee. Please join me in congratulating Gunther! Thanks. Carl signature.asc Description: Digital signature
Re: Build seems broken
I've pushed something that I didn't want couple of minutes ago and then force push to remove it. I'm not sure whether it's caused by that though. Jarcec On Mon, Nov 25, 2013 at 06:04:34PM -0800, Xuefu Zhang wrote: [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.604s [INFO] Finished at: Mon Nov 25 17:53:20 PST 2013 [INFO] Final Memory: 29M/283M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project hive-it-util: Compilation failure: Compilation failure: [ERROR] /home/xzhang/apa/hive-commit/itests/util/src/main/java/org/apache/hadoop/hive/ql/hooks/OptrStatGroupByHook.java:[45,73] cannot find symbol [ERROR] symbol : variable HIVEJOBPROGRESS [ERROR] location: class org.apache.hadoop.hive.conf.HiveConf.ConfVars [ERROR] /home/xzhang/apa/hive-commit/itests/util/src/main/java/org/apache/hadoop/hive/ql/hooks/OptrStatGroupByHook.java:[57,38] cannot find symbol [ERROR] symbol : method getCounters() [ERROR] location: class org.apache.hadoop.hive.ql.exec.Operatorcapture#671 of ? extends org.apache.hadoop.hive.ql.plan.OperatorDesc [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :hive-it-util signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive Committers - Jitendra Nath Pandey and Eric Hanson
Congratulations, good job! Jarcec On Thu, Nov 21, 2013 at 03:29:07PM -0800, Carl Steinbach wrote: The Apache Hive PMC has voted to make Jitendra Nath Pandey and Eric Hanson committers on the Apache Hive project. Please join me in congratulating Jitendra and Eric! Thanks. Carl signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive Committer and PMC Member - Lefty Leverenz
Congratulations Lefty! Jarcec On Sat, Nov 16, 2013 at 09:20:00PM -0800, Carl Steinbach wrote: The Apache Hive PMC has voted to make Lefty Leverenz a committer and PMC member on the Apache Hive Project. Please join me in congratulating Lefty! Thanks. Carl signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive PMC Member - Harish Butani
Congratulations, good job! Jarcec On Thu, Nov 14, 2013 at 05:17:46PM -0800, Carl Steinbach wrote: I am pleased to announce that Harish Butani has been elected to the Hive Project Management Committee. Please join me in congratulating Harish! Thanks. Carl signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive Committer - Prasad Mujumdar
Congratulations Prasad, good job! Jarcec On Sun, Nov 10, 2013 at 06:42:45PM -0800, Carl Steinbach wrote: The Apache Hive PMC has voted to make Prasad Mujumdar a committer on the Apache Hive Project. Please join me in congratulating Prasad! Thanks. Carl signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive Committer - Xuefu Zhang
Excellent job Xuefu, congratulations! Jarcec On Sun, Nov 03, 2013 at 08:06:07PM -0800, Carl Steinbach wrote: The Apache Hive PMC has voted to make Xuefu Zhang a committer on the Apache Hive project. Please join me in congratulating Xuefu! Thanks. Carl signature.asc Description: Digital signature
[jira] [Created] (HIVE-5733) Publish hive-exec artifact without all the dependencies
Jarek Jarcec Cecho created HIVE-5733:
Summary: Publish hive-exec artifact without all the dependencies
Key: HIVE-5733
URL: https://issues.apache.org/jira/browse/HIVE-5733
Project: Hive
Issue Type: Bug
Affects Versions: 0.12.0
Reporter: Jarek Jarcec Cecho
Currently the artifact {{hive-exec}} that is available in
[maven|http://search.maven.org/remotecontent?filepath=org/apache/hive/hive-exec/0.12.0/hive-exec-0.12.0.jar]
is shadowing all the dependencies (= the jar contains all Hive's
dependencies). As other projects that are depending on Hive might be use
slightly different version of the dependencies, it can easily happens that
Hive's shadowed version will be used instead which leads to very time consuming
debugging of what is happening (for example SQOOP-1198).
Would it be feasible publish {{hive-exec}} jar that will be build without
shadowing any dependency? For example
[avro-tools|http://search.maven.org/#artifactdetails%7Corg.apache.avro%7Cavro-tools%7C1.7.5%7Cjar]
is having classifier nodeps that represents artifact without any
dependencies.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Re: FYI Hive trunk has moved to maven
That is awesome news Brock, thank you very much for doing all the hard work! Jarcec On Thu, Oct 31, 2013 at 02:11:40PM -0500, Brock Noland wrote: More details here https://issues.apache.org/jira/browse/HIVE-5610 How to configure your development environment is here: https://cwiki.apache.org/confluence/display/Hive/HiveDeveloperFAQ signature.asc Description: Digital signature
[jira] [Updated] (HIVE-4723) DDLSemanticAnalyzer.addTablePartsOutputs eats several exceptions
[
https://issues.apache.org/jira/browse/HIVE-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4723:
-
Assignee: Jarek Jarcec Cecho (was: Szehon Ho)
DDLSemanticAnalyzer.addTablePartsOutputs eats several exceptions
Key: HIVE-4723
URL: https://issues.apache.org/jira/browse/HIVE-4723
Project: Hive
Issue Type: Bug
Reporter: Brock Noland
Assignee: Jarek Jarcec Cecho
I accidently tried to archive a partition on a non-partitioned table. The
error message was bad, hive ate an exception, and NPE'ed.
{noformat}
2013-06-09 16:36:12,628 ERROR parse.DDLSemanticAnalyzer
(DDLSemanticAnalyzer.java:addTablePartsOutputs(2899)) - Got HiveException
during obtaining list of partitions
2013-06-09 16:36:12,628 ERROR ql.Driver (SessionState.java:printError(383)) -
FAILED: NullPointerException null
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.addTablePartsOutputs(DDLSemanticAnalyzer.java:2912)
at
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.addTablePartsOutputs(DDLSemanticAnalyzer.java:2877)
at
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAlterTableArchive(DDLSemanticAnalyzer.java:2730)
at
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeInternal(DDLSemanticAnalyzer.java:316)
at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:277)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:433)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:337)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:902)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:259)
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.executeDriver(CliDriver.java:782)
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:156)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (HIVE-4723) DDLSemanticAnalyzer.addTablePartsOutputs eats several exceptions
[
https://issues.apache.org/jira/browse/HIVE-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4723:
-
Assignee: Szehon Ho (was: Jarek Jarcec Cecho)
DDLSemanticAnalyzer.addTablePartsOutputs eats several exceptions
Key: HIVE-4723
URL: https://issues.apache.org/jira/browse/HIVE-4723
Project: Hive
Issue Type: Bug
Reporter: Brock Noland
Assignee: Szehon Ho
I accidently tried to archive a partition on a non-partitioned table. The
error message was bad, hive ate an exception, and NPE'ed.
{noformat}
2013-06-09 16:36:12,628 ERROR parse.DDLSemanticAnalyzer
(DDLSemanticAnalyzer.java:addTablePartsOutputs(2899)) - Got HiveException
during obtaining list of partitions
2013-06-09 16:36:12,628 ERROR ql.Driver (SessionState.java:printError(383)) -
FAILED: NullPointerException null
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.addTablePartsOutputs(DDLSemanticAnalyzer.java:2912)
at
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.addTablePartsOutputs(DDLSemanticAnalyzer.java:2877)
at
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeAlterTableArchive(DDLSemanticAnalyzer.java:2730)
at
org.apache.hadoop.hive.ql.parse.DDLSemanticAnalyzer.analyzeInternal(DDLSemanticAnalyzer.java:316)
at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:277)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:433)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:337)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:902)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:259)
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.executeDriver(CliDriver.java:782)
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:156)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Re: [ANNOUNCE] New Hive PMC Members - Thejas Nair and Brock Noland
Awesome job guys, congratulations! Jarcec On Thu, Oct 24, 2013 at 03:10:33PM -0700, Carl Steinbach wrote: I am pleased to announce that Thejas Nair and Brock Noland have been elected to the Hive Project Management Committee. Please join me in congratulating Thejas and Brock! Thanks. Carl signature.asc Description: Digital signature
[jira] [Commented] (HIVE-5255) Missing metastore schema files for version 0.11
[ https://issues.apache.org/jira/browse/HIVE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13764081#comment-13764081 ] Jarek Jarcec Cecho commented on HIVE-5255: -- Thank you [~brocknoland]! Missing metastore schema files for version 0.11 --- Key: HIVE-5255 URL: https://issues.apache.org/jira/browse/HIVE-5255 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.11.0 Reporter: Jarek Jarcec Cecho Assignee: Jarek Jarcec Cecho Fix For: 0.12.0 Attachments: HIVE-5255.patch I've noticed that we are missing metastore schema and upgrade files for version 0.11. I know that the metastore structure has not been changed between 0.10 and 0.11, thus they are not strictly necessary. However in the same situation in the past (for example when going 0.2 - 0.3 or 0.8 - 0.9) we've always copied the metastore files from previous release. I believe that this is more user friendly approach as user can simply use the metastore schema file for his version without thinking which file to use. I know that 0.11 is out and that we are currently working on 0.12, but I believe that we should add those files retrospectively anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-5255) Missing metastore schema files for version 0.11
Jarek Jarcec Cecho created HIVE-5255: Summary: Missing metastore schema files for version 0.11 Key: HIVE-5255 URL: https://issues.apache.org/jira/browse/HIVE-5255 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.11.0 Reporter: Jarek Jarcec Cecho Assignee: Jarek Jarcec Cecho Fix For: 0.12.0 I've noticed that we are missing metastore schema and upgrade files for version 0.11. I know that the metastore structure has not been changed between 0.10 and 0.11, thus they are not strictly necessary. However in the same situation in the past (for example when going 0.2 - 0.3 or 0.8 - 0.9) we've always copied the metastore files from previous release. I believe that this is more user friendly approach as user can simply use the metastore schema file for his version without thinking which file to use. I know that 0.11 is out and that we are currently working on 0.12, but I believe that we should add those files retrospectively anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5255) Missing metastore schema files for version 0.11
[ https://issues.apache.org/jira/browse/HIVE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated HIVE-5255: - Attachment: HIVE-5255.patch The patch seems very big, but it's quite simple in nature. All I've done is to copy the metastore schema files from 0.10 as 0.11 and provided empty upgrade scrips. Missing metastore schema files for version 0.11 --- Key: HIVE-5255 URL: https://issues.apache.org/jira/browse/HIVE-5255 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.11.0 Reporter: Jarek Jarcec Cecho Assignee: Jarek Jarcec Cecho Fix For: 0.12.0 Attachments: HIVE-5255.patch I've noticed that we are missing metastore schema and upgrade files for version 0.11. I know that the metastore structure has not been changed between 0.10 and 0.11, thus they are not strictly necessary. However in the same situation in the past (for example when going 0.2 - 0.3 or 0.8 - 0.9) we've always copied the metastore files from previous release. I believe that this is more user friendly approach as user can simply use the metastore schema file for his version without thinking which file to use. I know that 0.11 is out and that we are currently working on 0.12, but I believe that we should add those files retrospectively anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5255) Missing metastore schema files for version 0.11
[ https://issues.apache.org/jira/browse/HIVE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated HIVE-5255: - Status: Patch Available (was: Open) Missing metastore schema files for version 0.11 --- Key: HIVE-5255 URL: https://issues.apache.org/jira/browse/HIVE-5255 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.11.0 Reporter: Jarek Jarcec Cecho Assignee: Jarek Jarcec Cecho Fix For: 0.12.0 Attachments: HIVE-5255.patch I've noticed that we are missing metastore schema and upgrade files for version 0.11. I know that the metastore structure has not been changed between 0.10 and 0.11, thus they are not strictly necessary. However in the same situation in the past (for example when going 0.2 - 0.3 or 0.8 - 0.9) we've always copied the metastore files from previous release. I believe that this is more user friendly approach as user can simply use the metastore schema file for his version without thinking which file to use. I know that 0.11 is out and that we are currently working on 0.12, but I believe that we should add those files retrospectively anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-5255) Missing metastore schema files for version 0.11
[ https://issues.apache.org/jira/browse/HIVE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762936#comment-13762936 ] Jarek Jarcec Cecho commented on HIVE-5255: -- The test failures do not seem to be relevant for this patch. Missing metastore schema files for version 0.11 --- Key: HIVE-5255 URL: https://issues.apache.org/jira/browse/HIVE-5255 Project: Hive Issue Type: Bug Components: Metastore Affects Versions: 0.11.0 Reporter: Jarek Jarcec Cecho Assignee: Jarek Jarcec Cecho Fix For: 0.12.0 Attachments: HIVE-5255.patch I've noticed that we are missing metastore schema and upgrade files for version 0.11. I know that the metastore structure has not been changed between 0.10 and 0.11, thus they are not strictly necessary. However in the same situation in the past (for example when going 0.2 - 0.3 or 0.8 - 0.9) we've always copied the metastore files from previous release. I believe that this is more user friendly approach as user can simply use the metastore schema file for his version without thinking which file to use. I know that 0.11 is out and that we are currently working on 0.12, but I believe that we should add those files retrospectively anyway. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANNOUNCE] New Hive Committer - Yin Huai
Congratulations Yin! Jarcec On Tue, Sep 03, 2013 at 09:49:55PM -0700, Carl Steinbach wrote: The Apache Hive PMC has voted to make Yin Huai a committer on the Apache Hive project. Please join me in congratulating Yin! Thanks. Carl signature.asc Description: Digital signature
[jira] [Created] (HIVE-5210) WebHCatJTShim implementations are missing Apache license headers
Jarek Jarcec Cecho created HIVE-5210:
Summary: WebHCatJTShim implementations are missing Apache license
headers
Key: HIVE-5210
URL: https://issues.apache.org/jira/browse/HIVE-5210
Project: Hive
Issue Type: Bug
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.12.0
During investigation of SQOOP-1190, I've noticed that {{WebHCatJTShim}}
implementaion files do not have license headers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5210) WebHCatJTShim implementations are missing Apache license headers
[
https://issues.apache.org/jira/browse/HIVE-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-5210:
-
Attachment: HIVE-5210.patch
WebHCatJTShim implementations are missing Apache license headers
Key: HIVE-5210
URL: https://issues.apache.org/jira/browse/HIVE-5210
Project: Hive
Issue Type: Bug
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.12.0
Attachments: HIVE-5210.patch
During investigation of SQOOP-1190, I've noticed that {{WebHCatJTShim}}
implementaion files do not have license headers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-5210) WebHCatJTShim implementations are missing Apache license headers
[
https://issues.apache.org/jira/browse/HIVE-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-5210:
-
Status: Patch Available (was: Open)
WebHCatJTShim implementations are missing Apache license headers
Key: HIVE-5210
URL: https://issues.apache.org/jira/browse/HIVE-5210
Project: Hive
Issue Type: Bug
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.12.0
Attachments: HIVE-5210.patch
During investigation of SQOOP-1190, I've noticed that {{WebHCatJTShim}}
implementaion files do not have license headers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-5210) WebHCatJTShim implementations are missing Apache license headers
[
https://issues.apache.org/jira/browse/HIVE-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13757764#comment-13757764
]
Jarek Jarcec Cecho commented on HIVE-5210:
--
The test failures do not seem to be relevant to this patch.
WebHCatJTShim implementations are missing Apache license headers
Key: HIVE-5210
URL: https://issues.apache.org/jira/browse/HIVE-5210
Project: Hive
Issue Type: Bug
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.12.0
Attachments: HIVE-5210.patch
During investigation of SQOOP-1190, I've noticed that {{WebHCatJTShim}}
implementaion files do not have license headers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANNOUNCE] New Hive Committer - Thejas Nair
Congratulations Thejas! Jarcec On Tue, Aug 20, 2013 at 03:31:48AM -0700, Carl Steinbach wrote: The Apache Hive PMC has voted to make Thejas Nair a committer on the Apache Hive project. Please join me in congratulating Thejas! signature.asc Description: Digital signature
[jira] [Updated] (HIVE-4355) HCatalog test TestPigHCatUtil might fail on JDK7
[
https://issues.apache.org/jira/browse/HIVE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4355:
-
Attachment: HIVE-4355.patch
HCatalog test TestPigHCatUtil might fail on JDK7
Key: HIVE-4355
URL: https://issues.apache.org/jira/browse/HIVE-4355
Project: Hive
Issue Type: Sub-task
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Attachments: HIVE-4355.patch, HIVE-4355.patch
I’ve tried interesting scenario. I’ve compiled hcatalog with JDK 6 (including
tests) and run the tests itself on JDK 7. My motivation was to see what will
happen to users that will download official Apache release (usually compiled
on JDK 6) and will run it on JDK 7. I’ve seen {{TestPigHCatUtil}} failing
because the order of method calls was different then when compiling and
running the tests only on JDK 6 or only on JDK 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4355) HCatalog test TestPigHCatUtil might fail on JDK7
[
https://issues.apache.org/jira/browse/HIVE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740525#comment-13740525
]
Jarek Jarcec Cecho commented on HIVE-4355:
--
[~xuefuz], definitely, thank you for pointing that out! I'm not sure why I did
not do that first time...
HCatalog test TestPigHCatUtil might fail on JDK7
Key: HIVE-4355
URL: https://issues.apache.org/jira/browse/HIVE-4355
Project: Hive
Issue Type: Sub-task
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Attachments: HIVE-4355.patch, HIVE-4355.patch
I’ve tried interesting scenario. I’ve compiled hcatalog with JDK 6 (including
tests) and run the tests itself on JDK 7. My motivation was to see what will
happen to users that will download official Apache release (usually compiled
on JDK 6) and will run it on JDK 7. I’ve seen {{TestPigHCatUtil}} failing
because the order of method calls was different then when compiling and
running the tests only on JDK 6 or only on JDK 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4355) HCatalog test TestPigHCatUtil might fail on JDK7
[
https://issues.apache.org/jira/browse/HIVE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13738356#comment-13738356
]
Jarek Jarcec Cecho commented on HIVE-4355:
--
Hi [~ashutoshc],
thank you very much for taking a look on this patch! Please accept my apologies
for late response, I've unfortunately completely missed the updates.
The issue here is that method {{testGetBagSubSchemaConfigured}} is setting
System properties in order to test the behavior, but it's not cleaning them
after the test. This do not appear to be an issue on pure JDK6 as the method
{{testGetBagSubSchema}} is being executed before
{{testGetBagSubSchemaConfigured}}. However when I compiled the tests with JDK6
and then executed them on JDK7, the order in which the two testing methods are
executed has changed - the method {{testGetBagSubSchemaConfigured}} was
executed before {{testGetBagSubSchema}}. As the
{{testGetBagSubSchemaConfigured}} was not cleaning up the System properties,
the second method {{testGetBagSubSchema}} has picked them up and the test
itself has failed. Hope that it helps!
HCatalog test TestPigHCatUtil might fail on JDK7
Key: HIVE-4355
URL: https://issues.apache.org/jira/browse/HIVE-4355
Project: Hive
Issue Type: Sub-task
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Attachments: HIVE-4355.patch
I’ve tried interesting scenario. I’ve compiled hcatalog with JDK 6 (including
tests) and run the tests itself on JDK 7. My motivation was to see what will
happen to users that will download official Apache release (usually compiled
on JDK 6) and will run it on JDK 7. I’ve seen {{TestPigHCatUtil}} failing
because the order of method calls was different then when compiling and
running the tests only on JDK 6 or only on JDK 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4355) HCatalog test TestPigHCatUtil might fail on JDK7
[
https://issues.apache.org/jira/browse/HIVE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4355:
-
Status: Patch Available (was: Open)
Putting back status Patch available as the explanation was provided.
HCatalog test TestPigHCatUtil might fail on JDK7
Key: HIVE-4355
URL: https://issues.apache.org/jira/browse/HIVE-4355
Project: Hive
Issue Type: Sub-task
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Attachments: HIVE-4355.patch
I’ve tried interesting scenario. I’ve compiled hcatalog with JDK 6 (including
tests) and run the tests itself on JDK 7. My motivation was to see what will
happen to users that will download official Apache release (usually compiled
on JDK 6) and will run it on JDK 7. I’ve seen {{TestPigHCatUtil}} failing
because the order of method calls was different then when compiling and
running the tests only on JDK 6 or only on JDK 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4876) Beeling help text do not contain -f and -e parameters
[
https://issues.apache.org/jira/browse/HIVE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13717903#comment-13717903
]
Jarek Jarcec Cecho commented on HIVE-4876:
--
Hi [~brocknoland], thank you very much for reviewing this patch!
Beeling help text do not contain -f and -e parameters
-
Key: HIVE-4876
URL: https://issues.apache.org/jira/browse/HIVE-4876
Project: Hive
Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Trivial
Attachments: bugHIVE-4876.patch, HIVE-4876.patch
I've noticed that beeline do have support for {{-e}} and {{-f}} parameters,
however those are not documented in the help text that can be retrieved by
calling beeline with parameter {{-h}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANNOUNCE] New Hive Committer - Gunther Hagleitner
Congratulations Gunther! Jarcec On Sun, Jul 21, 2013 at 01:00:31AM -0700, Carl Steinbach wrote: The Apache Hive PMC has voted to make Gunther Hagleitner a committer on the Apache Hive project. Congratulations Gunther! Carl signature.asc Description: Digital signature
[jira] [Updated] (HIVE-4876) Beeling help text do not contain -f and -e parameters
[
https://issues.apache.org/jira/browse/HIVE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4876:
-
Attachment: HIVE-4876.patch
Beeling help text do not contain -f and -e parameters
-
Key: HIVE-4876
URL: https://issues.apache.org/jira/browse/HIVE-4876
Project: Hive
Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Trivial
Attachments: bugHIVE-4876.patch, HIVE-4876.patch
I've noticed that beeline do have support for {{-e}} and {{-f}} parameters,
however those are not documented in the help text that can be retrieved by
calling beeline with parameter {{-h}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4876) Beeling help text do not contain -f and -e parameters
[
https://issues.apache.org/jira/browse/HIVE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13714719#comment-13714719
]
Jarek Jarcec Cecho commented on HIVE-4876:
--
[~brocknoland], attached, thank you for your note!
Beeling help text do not contain -f and -e parameters
-
Key: HIVE-4876
URL: https://issues.apache.org/jira/browse/HIVE-4876
Project: Hive
Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Trivial
Attachments: bugHIVE-4876.patch, HIVE-4876.patch
I've noticed that beeline do have support for {{-e}} and {{-f}} parameters,
however those are not documented in the help text that can be retrieved by
calling beeline with parameter {{-h}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: VOTE: moving hive from forest to Apache CMS
+1 (non-binding) Jarcec On Sun, Jul 21, 2013 at 01:53:39PM -0400, Edward Capriolo wrote: http://hive.apache.org is generated by forest, a rather cumbersome and confusing way to run a website. Forest is difficult to maintain and publish updates with. As a nail in the coffin forest does not even work well with recent versions of java. This vote is to move the site to: Apache CMShttps://www.apache.org/dev/cms.html and away from forest. Brock Noland has offered to move the site, and I am offering to help him and look it over. Vote +1 if you support the move to Apache CMS. (This is the one case where cutting down a forest is a very good idea :) Edward signature.asc Description: Digital signature
[jira] [Created] (HIVE-4876) Beeling help text do not contain -f and -e parameters
Jarek Jarcec Cecho created HIVE-4876:
Summary: Beeling help text do not contain -f and -e parameters
Key: HIVE-4876
URL: https://issues.apache.org/jira/browse/HIVE-4876
Project: Hive
Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Trivial
I've noticed that beeline do have support for {{-e}} and {{-f}} parameters,
however those are not documented in the help text that can be retrieved by
calling beeline with parameter {{-h}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4876) Beeling help text do not contain -f and -e parameters
[
https://issues.apache.org/jira/browse/HIVE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4876:
-
Attachment: bugHIVE-4876.patch
Beeling help text do not contain -f and -e parameters
-
Key: HIVE-4876
URL: https://issues.apache.org/jira/browse/HIVE-4876
Project: Hive
Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Trivial
Attachments: bugHIVE-4876.patch
I've noticed that beeline do have support for {{-e}} and {{-f}} parameters,
however those are not documented in the help text that can be retrieved by
calling beeline with parameter {{-h}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANNOUNCE] New Hive Committer - Brock Noland
Congratulations Brock! Jarcec On Mon, Jul 15, 2013 at 10:29:51PM -0700, Carl Steinbach wrote: The Apache Hive PMC has passed a vote to make Brock Noland a new committer on the project. Brock, please submit your ICLA to the Apache Software Foundation as described here: http://www.apache.org/licenses/#clas Thanks. Carl signature.asc Description: Digital signature
[jira] [Updated] (HIVE-4459) Script hcat is overriding HIVE_CONF_DIR variable
[
https://issues.apache.org/jira/browse/HIVE-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4459:
-
Attachment: bugHIVE-4459.patch
Script hcat is overriding HIVE_CONF_DIR variable
Key: HIVE-4459
URL: https://issues.apache.org/jira/browse/HIVE-4459
Project: Hive
Issue Type: Improvement
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Minor
Attachments: bugHIVE-4459.patch
Script {{hcat}} is currently overriding variable {{HIVE_CONF_DIR}} to
{{$\{HIVE_HOME}/conf}}. It would be useful to use the previous content of the
variable if it was set by the user.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4459) Script hcat is overriding HIVE_CONF_DIR variable
[
https://issues.apache.org/jira/browse/HIVE-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4459:
-
Fix Version/s: 0.12.0
Status: Patch Available (was: Open)
Script hcat is overriding HIVE_CONF_DIR variable
Key: HIVE-4459
URL: https://issues.apache.org/jira/browse/HIVE-4459
Project: Hive
Issue Type: Improvement
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Minor
Fix For: 0.12.0
Attachments: bugHIVE-4459.patch
Script {{hcat}} is currently overriding variable {{HIVE_CONF_DIR}} to
{{$\{HIVE_HOME}/conf}}. It would be useful to use the previous content of the
variable if it was set by the user.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: hi
Hi Namit, I like your proposal very much and I would take it a bit further: 1. ... For any complex function, clear examples (input/output) would really help. I'm concerned that examples in the code (comments) might very quickly become obsolete as it can very easily happen that someone will change the code without changing the example. What about using for this purpose normal unit tests? Developers will still be able to see the expected input/output, but in addition we will have automatic way how to detect (possibly incompatible) changes. Please note that I'm not suggesting to abandon the *.q file tests, just to also include unit tests for complex methods. Jarcec On Thu, Apr 18, 2013 at 12:31:10PM +, Namit Jain wrote: Hi, Since we are developing at a very fast pace, it would be really useful to think about maintainability and testing of the large codebase. Historically, we have not focussed on a few things, and they might soon bite us. I wanted to propose the following for all checkins: 1. Javadoc for all public/private functions, except for setters/getters. For any complex function, clear examples (input/output) would really help. 2. Convention for variable/function names – do we have any ? 3. If possible, the test name (.q file) where the function is being invoked, or the query which would potentially test that scenario, if it is a query processor change. 4. Specially, for query optimizations, it might be a good idea to have a simple working query at the top, and the expected changes. For e.g.. The operator tree for that query at each step, or a detailed explanation at the top. 5. Comments in each test (.q file)– that should include the jira number, what is it trying to test. Assumptions about each query. 6. Reduce the output for each test – whenever query is outputting more than 10 results, it should have a reason. Otherwise, each query result should be bounded by 10 rows. In general, focussing on a lot of comments in the code will go a long way for everyone to follow along. Thanks, -namit signature.asc Description: Digital signature
Re: [ANNOUNCE] New Hive Committers: Harish Butani and Owen O'Malley
Congratulations, great job! Jarcec On Mon, Apr 15, 2013 at 12:30:28PM -0700, Carl Steinbach wrote: The Hive PMC has voted to make Harish Butani and Owen O'Malley committers on the Apache Hive Project. A list of Harish's contributions to the project can be seen here: http://s.apache.org/n3h Owen's contributions can be seen here: http://s.apache.org/wQm Please join me in congratulating Harish and Owen! Thanks. Carl signature.asc Description: Digital signature
[jira] [Updated] (HIVE-4355) HCatalog test TestPigHCatUtil might fail on JDK7
[
https://issues.apache.org/jira/browse/HIVE-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4355:
-
Status: Patch Available (was: Open)
HCatalog test TestPigHCatUtil might fail on JDK7
Key: HIVE-4355
URL: https://issues.apache.org/jira/browse/HIVE-4355
Project: Hive
Issue Type: Bug
Components: HCatalog
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Attachments: HIVE-4355.patch
I’ve tried interesting scenario. I’ve compiled hcatalog with JDK 6 (including
tests) and run the tests itself on JDK 7. My motivation was to see what will
happen to users that will download official Apache release (usually compiled
on JDK 6) and will run it on JDK 7. I’ve seen {{TestPigHCatUtil}} failing
because the order of method calls was different then when compiling and
running the tests only on JDK 6 or only on JDK 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3964) HIVE-3649.oracle.sql must update SDS table for IS_STOREDASSUBDIRECTORIES
[
https://issues.apache.org/jira/browse/HIVE-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601606#comment-13601606
]
Jarek Jarcec Cecho commented on HIVE-3964:
--
+1 (non-binding).
We might want to backport also the other schema upgrade patches that were
pushed to trunk. Namely HIVE-4024, HIVE-4021, HIVE-3999 and HIVE-3995.
Jarcec
HIVE-3649.oracle.sql must update SDS table for IS_STOREDASSUBDIRECTORIES
Key: HIVE-3964
URL: https://issues.apache.org/jira/browse/HIVE-3964
Project: Hive
Issue Type: Bug
Reporter: Mithun Radhakrishnan
Assignee: Mithun Radhakrishnan
Attachments: HIVE-3964.branch10.patch
The metastore-update script is available now on trunk/. (As part of
HIVE-3931.)
However, on branch-10, the 011-HIVE-3649.oracle.sql script (that updates the
SDS table) introduces a non-NULL constraint on a new field (that doesn't
exist in the old schema). The correct way to update the SDS table is as it's
done in trunk/:
{{ALTER TABLE SDS ADD IS_STOREDASSUBDIRECTORIES NUMBER(1) NULL;}}
{{UPDATE SDS SET IS_STOREDASSUBDIRECTORIES = 0;}}
{{ALTER TABLE SDS MODIFY(IS_STOREDASSUBDIRECTORIES NOT NULL);}}
We need to merge this change into branch-0.10/.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4141) InspectorFactories contains static HashMaps which can cause infinite loop
[ https://issues.apache.org/jira/browse/HIVE-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13597991#comment-13597991 ] Jarek Jarcec Cecho commented on HIVE-4141: -- +1 (non-binding) InspectorFactories contains static HashMaps which can cause infinite loop - Key: HIVE-4141 URL: https://issues.apache.org/jira/browse/HIVE-4141 Project: Hive Issue Type: Sub-task Components: Server Infrastructure Reporter: Brock Noland Attachments: HIVE-4141-1.patch When many clients hit hs2, hs2 can get stuck in an infinite loop due to concurrent modification of the static maps here: https://github.com/apache/hive/blob/trunk/serde/src/java/org/apache/hadoop/hive/serde2/lazy/objectinspector/LazyObjectInspectorFactory.java and in other ObjectFactories. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [ANNOUNCE] Kevin Wilfong elected to Hive PMC
Awesome job, congratulations Kevin! Jarcec On Mon, Mar 04, 2013 at 11:54:36AM -0800, Carl Steinbach wrote: On behalf of the Apache Hive PMC I am pleased to welcome Kevin Wilfong as a member of the Apache Hive PMC. Please join me in congratulating Kevin on his new role! Thanks. Carl signature.asc Description: Digital signature
[jira] [Commented] (HIVE-4007) Create abstract classes for serializer and deserializer
[ https://issues.apache.org/jira/browse/HIVE-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13589604#comment-13589604 ] Jarek Jarcec Cecho commented on HIVE-4007: -- I'm still +1 (non-binding), thank you Namit for working on this! Jarcec Create abstract classes for serializer and deserializer --- Key: HIVE-4007 URL: https://issues.apache.org/jira/browse/HIVE-4007 Project: Hive Issue Type: Improvement Components: Serializers/Deserializers Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.4007.1.patch, hive.4007.2.patch, hive.4007.3.patch, hive.4007.4.patch Currently, it is very difficult to change the Serializer/Deserializer interface, since all the SerDes directly implement the interface. Instead, we should have abstract classes for implementing these interfaces. In case of a interface change, only the abstract class and the relevant serde needs to change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4086) Cross Database Support for Indexes and Partitions (or all DDL statements)
[
https://issues.apache.org/jira/browse/HIVE-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588626#comment-13588626
]
Jarek Jarcec Cecho commented on HIVE-4086:
--
Hi Todd,
thank you very much for reporting this issue. We already have JIRA HIVE-4064 to
track this requirement so I'm closing this one as a duplicate to keep all the
information in one place.
To immediately unblock you, did you consider using SQL query {{USE dbname}}
to change working database from {{default}} to {{dbname}}?
Jarcec
Cross Database Support for Indexes and Partitions (or all DDL statements)
-
Key: HIVE-4086
URL: https://issues.apache.org/jira/browse/HIVE-4086
Project: Hive
Issue Type: Improvement
Components: Database/Schema, ODBC, SQL
Affects Versions: 0.9.0
Environment: Writing a query tool in .NET connecting with ODBC to
Hadoop on Linux.
Reporter: Todd Wilson
I'd like to see more cross-database support. I'm using a Cloudera
implementation on Hive .9. Currently, you can create new databases, you can
create tables and views in those databases, but you cannot create indexes or
partitions on those tables. Likewise, commands like show partitions or show
indexes will only work on table in the default database. This would probably
also affect statements like Alter Table and Recover Partitions. Probably
also something like Create Function, but if you want to keep all functions
being created in the default database that would work. I would be more
interested in full cross-database support for tables and views to start.
Functions for example could all be created in default. Thank you.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-4086) Cross Database Support for Indexes and Partitions (or all DDL statements)
[ https://issues.apache.org/jira/browse/HIVE-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho resolved HIVE-4086. -- Resolution: Duplicate Cross Database Support for Indexes and Partitions (or all DDL statements) - Key: HIVE-4086 URL: https://issues.apache.org/jira/browse/HIVE-4086 Project: Hive Issue Type: Improvement Components: Database/Schema, ODBC, SQL Affects Versions: 0.9.0 Environment: Writing a query tool in .NET connecting with ODBC to Hadoop on Linux. Reporter: Todd Wilson I'd like to see more cross-database support. I'm using a Cloudera implementation on Hive .9. Currently, you can create new databases, you can create tables and views in those databases, but you cannot create indexes or partitions on those tables. Likewise, commands like show partitions or show indexes will only work on table in the default database. This would probably also affect statements like Alter Table and Recover Partitions. Probably also something like Create Function, but if you want to keep all functions being created in the default database that would work. I would be more interested in full cross-database support for tables and views to start. Functions for example could all be created in default. Thank you. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Issue involving non-sun java build
Hi Renata, I'm glad to see you interested in contributing to Hive community! Please don't hesitate and follow the link provided by Brock in previous email if you're interested. I just wanted to add that Hive is a Hadoop SQL Engine and thus we have major dependencies on Hadoop. Whereas extending Hive ability to work on other JDKs is definitely a great thing to do, I feel the need to warn that you might get into issues as Hadoop itself might not work on those JDKs. I know about following wiki page [1] that describes the support of various JDKs in Hadoop, but it seems not maintained any more. Jarcec Links: 1: http://wiki.apache.org/hadoop/HadoopJavaVersions On Wed, Feb 27, 2013 at 11:01:58AM -0600, Brock Noland wrote: Hi, I think we'd want hive to work on as many JVM's as feasible. With that said, since it's tested mostly on Sun JVM, it's possible we'll introduce new issues in the future so you'll need to keep testing. Here is a guide on how to contribute: https://cwiki.apache.org/confluence/display/Hive/HowToContribute Glad to have you interested! Brock On Wed, Feb 27, 2013 at 10:06 AM, Renata Ghisloti Duarte de Souza rgdua...@linux.vnet.ibm.com wrote: Hello, I've been working with Hive for a couple of months now, and although it is a pretty strong framework, I can't help but noticing that some testcases fails on Non-Sun Java. Some examples are: TestCliDriver, TestParse and TestJdbcDriver. The issues involve HashMap situation, where Sun Java has a different output order than Non-Sun Java. It is a silly problem, but it does cause failures. I've been working on fixes for theses problems, and was planning to contribute it. Is this something the Hive community would be interested in? What are your thoughts about that? Thanks, Renata. -- Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/ signature.asc Description: Digital signature
[jira] [Commented] (HIVE-4086) Cross Database Support for Indexes and Partitions (or all DDL statements)
[
https://issues.apache.org/jira/browse/HIVE-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588849#comment-13588849
]
Jarek Jarcec Cecho commented on HIVE-4086:
--
The {{USE db}} definitely works in hive shell and JDBC interface. I can't speak
for the ODBC drivers unfortunately.
Cross Database Support for Indexes and Partitions (or all DDL statements)
-
Key: HIVE-4086
URL: https://issues.apache.org/jira/browse/HIVE-4086
Project: Hive
Issue Type: Improvement
Components: Database/Schema, ODBC, SQL
Affects Versions: 0.9.0
Environment: Writing a query tool in .NET connecting with ODBC to
Hadoop on Linux.
Reporter: Todd Wilson
I'd like to see more cross-database support. I'm using a Cloudera
implementation on Hive .9. Currently, you can create new databases, you can
create tables and views in those databases, but you cannot create indexes or
partitions on those tables. Likewise, commands like show partitions or show
indexes will only work on table in the default database. This would probably
also affect statements like Alter Table and Recover Partitions. Probably
also something like Create Function, but if you want to keep all functions
being created in the default database that would work. I would be more
interested in full cross-database support for tables and views to start.
Functions for example could all be created in default. Thank you.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4064) Handle db qualified names consistently across all HiveQL statements
[
https://issues.apache.org/jira/browse/HIVE-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13584579#comment-13584579
]
Jarek Jarcec Cecho commented on HIVE-4064:
--
Another command that is not working consistently is:
{code}
ALTER TABLE db.table ...
{code}
Handle db qualified names consistently across all HiveQL statements
---
Key: HIVE-4064
URL: https://issues.apache.org/jira/browse/HIVE-4064
Project: Hive
Issue Type: Bug
Components: SQL
Affects Versions: 0.10.0
Reporter: Shreepadma Venugopalan
Hive doesn't consistently handle db qualified names across all HiveQL
statements. While some HiveQL statements such as SELECT support DB qualified
names, other such as CREATE INDEX doesn't.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: jdo2-api dependency
Hi Nitay, would you mind opening a JIRA for that? Jarcec On Fri, Feb 22, 2013 at 01:03:15PM -0500, Nitay Joffe wrote: Hey guys, The latest open source hive release (0.10.0) depends on javax.jdo artifact jdo2-api version 2.3-ec. This version is not actually in maven central, which means everyone who uses hive requires custom maven repository definitions which is discouraged by maven folks. I pinged the javax.jdo guys about it and they recommended we upgrade to 3.0. See http://mail-archives.apache.org/mod_mbox/db-jdo-dev/201302.mbox/%3CCAGZB7RguuEJnpVbtaqOgYEbsUNzP3aMSmM8SM8aOxcb-hLWwjg%40mail.gmail.com%3E for the conversation. Can you guys fix this? Thanks, - Nitay signature.asc Description: Digital signature
[jira] [Commented] (HIVE-4007) Create abstract classes for serializer and deserializer
[ https://issues.apache.org/jira/browse/HIVE-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13582260#comment-13582260 ] Jarek Jarcec Cecho commented on HIVE-4007: -- +1 (non-binding) Thank you for working on this Namit! Jarcec Create abstract classes for serializer and deserializer --- Key: HIVE-4007 URL: https://issues.apache.org/jira/browse/HIVE-4007 Project: Hive Issue Type: Improvement Components: Serializers/Deserializers Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.4007.1.patch, hive.4007.2.patch, hive.4007.3.patch Currently, it is very difficult to change the Serializer/Deserializer interface, since all the SerDes directly implement the interface. Instead, we should have abstract classes for implementing these interfaces. In case of a interface change, only the abstract class and the relevant serde needs to change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3980) Cleanup after HIVE-3403
[ https://issues.apache.org/jira/browse/HIVE-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13582267#comment-13582267 ] Jarek Jarcec Cecho commented on HIVE-3980: -- +1 (non-binding) Seems as a reasonable changes to me. Jacec Cleanup after HIVE-3403 --- Key: HIVE-3980 URL: https://issues.apache.org/jira/browse/HIVE-3980 Project: Hive Issue Type: Bug Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Attachments: hive.3980.1.patch, hive.3980.2.patch There have been a lot of comments on HIVE-3403, which involve changing variable names/function names/adding more comments/general cleanup etc. Since HIVE-3403 involves a lot of refactoring, it was fairly difficult to address the comments there, since refreshing becomes impossible. This jira is to track those cleanups. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3951) Allow Decimal type columns in Regex Serde
[ https://issues.apache.org/jira/browse/HIVE-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13582587#comment-13582587 ] Jarek Jarcec Cecho commented on HIVE-3951: -- +1 (non-binding) Allow Decimal type columns in Regex Serde - Key: HIVE-3951 URL: https://issues.apache.org/jira/browse/HIVE-3951 Project: Hive Issue Type: New Feature Components: Serializers/Deserializers Affects Versions: 0.10.0 Reporter: Mark Grover Assignee: Mark Grover Fix For: 0.11.0 Attachments: HIVE-3951.1.patch Decimal type in Hive was recently added by HIVE-2693. We should allow users to create tables with decimal type columns when using Regex Serde. HIVE-3004 did something similar for other primitive types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4007) Create abstract classes for serializer and deserializer
[
https://issues.apache.org/jira/browse/HIVE-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581395#comment-13581395
]
Jarek Jarcec Cecho commented on HIVE-4007:
--
Hi Namit,
thank you very much for working on this. I've took a look on the patch and I do
have one high level question. It seems to me that we're just adding
{{AbstractSerDe}} that all {{SerDe}} implementations will extend in the future
to allow the easy extension for future functionality. But it also seems that
we're keeping the old {{SerDe}} interface implementation. Since no {{SerDe}}
should implement that directly, it seems to me that it's unnecessary piece of
code. I can imagine that it would be great to keep it around for a release or
two to provide backward compatibility and allow Hive users to migrate they
codebase without immediately breaking the environment. I would suggest to mark
this interface as {{@Deprecated}} in case that this is the intent.
Jarcec
Create abstract classes for serializer and deserializer
---
Key: HIVE-4007
URL: https://issues.apache.org/jira/browse/HIVE-4007
Project: Hive
Issue Type: Improvement
Components: Serializers/Deserializers
Reporter: Namit Jain
Assignee: Namit Jain
Attachments: hive.4007.1.patch, hive.4007.2.patch
Currently, it is very difficult to change the Serializer/Deserializer
interface, since all the SerDes directly implement the interface.
Instead, we should have abstract classes for implementing these interfaces.
In case of a interface change, only the abstract class and the relevant
serde needs to change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load
[
https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580457#comment-13580457
]
Jarek Jarcec Cecho commented on HIVE-3999:
--
Hi sir,
setting the default value was one of the options that I've explored when
working on this JIRA. However I've decided not to use it and rather use three
step column addition (please checkout the patch). One of the reasons behind
this decision is that with no explicit default value, running old hive against
new metastore will fail. I believe that this is much safer as otherwise Hive
would continue to operate on updated schema repository and might eventually
corrupt the data.
Jarcec
Mysql metastore upgrade script will end up with different schema than the
full schema load
--
Key: HIVE-3999
URL: https://issues.apache.org/jira/browse/HIVE-3999
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.11.0
Attachments: mysql_upgrade_issue.patch
I've noticed that the file {{hive-schema-0.10.0.mysql.sql}} is creating table
SDS with following column:
{code}
`IS_STOREDASSUBDIRECTORIES` bit(1) NOT NULL,
{code}
However the upgrade script {{011-HIVE-3649.mysql.sql}} will create the column
differently:
{code}
ALTER TABLE `SDS` ADD `IS_STOREDASSUBDIRECTORIES` bit(1) ;
{code}
Thus user will get slightly different schema each time - once with NOT NULL
and secondly with NULL definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Adding user jarcec to contributor list on JIRA
Hi Hive developers, I was lately working on some small JIRAs and I'm unfortunately not able to assign those tickets to myself. As far as I know this is because I'm not in the contributor group in the Hive JIRA project configuration. Would someone with sufficient privileges add me there? This status should not grant me any additional privileges as far as know, so it should safe operation. Jarcec signature.asc Description: Digital signature
[jira] [Assigned] (HIVE-3998) Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
[
https://issues.apache.org/jira/browse/HIVE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho reassigned HIVE-3998:
Assignee: Jarek Jarcec Cecho
Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
Key: HIVE-3998
URL: https://issues.apache.org/jira/browse/HIVE-3998
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.11.0
Attachments: oracle_update_issue.patch
The problem is in following file {{011-HIVE-3649.oracle.sql}} that contains
following line:
{code}
alter table SDS add IS_STOREDASSUBDIRECTORIES NUMBER(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load
[
https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho reassigned HIVE-3999:
Assignee: Jarek Jarcec Cecho
Mysql metastore upgrade script will end up with different schema than the
full schema load
--
Key: HIVE-3999
URL: https://issues.apache.org/jira/browse/HIVE-3999
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Fix For: 0.11.0
Attachments: mysql_upgrade_issue.patch
I've noticed that the file {{hive-schema-0.10.0.mysql.sql}} is creating table
SDS with following column:
{code}
`IS_STOREDASSUBDIRECTORIES` bit(1) NOT NULL,
{code}
However the upgrade script {{011-HIVE-3649.mysql.sql}} will create the column
differently:
{code}
ALTER TABLE `SDS` ADD `IS_STOREDASSUBDIRECTORIES` bit(1) ;
{code}
Thus user will get slightly different schema each time - once with NOT NULL
and secondly with NULL definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-3995) PostgreSQL upgrade scripts are not valid
[ https://issues.apache.org/jira/browse/HIVE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho reassigned HIVE-3995: Assignee: Jarek Jarcec Cecho PostgreSQL upgrade scripts are not valid Key: HIVE-3995 URL: https://issues.apache.org/jira/browse/HIVE-3995 Project: Hive Issue Type: Bug Components: Metastore Reporter: Jarek Jarcec Cecho Assignee: Jarek Jarcec Cecho Fix For: 0.11.0 Attachments: postgre_update_issue.patch, postgre_update_issue.patch I've noticed that scripts for upgrading metastore backed up on PostgreSQL are not valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-4021) PostgreSQL upgrade scripts are creating column with incorrect name
[
https://issues.apache.org/jira/browse/HIVE-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho reassigned HIVE-4021:
Assignee: Jarek Jarcec Cecho
PostgreSQL upgrade scripts are creating column with incorrect name
--
Key: HIVE-4021
URL: https://issues.apache.org/jira/browse/HIVE-4021
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Trivial
Attachments: bugHIVE-4021.patch
I've noticed that PostgreSQL upgrade scripts are creating table
{{PART_COL_STATS}} and {{TAB_COL_STATS}} with column {{DOUBLE_HIGH_VALUES}},
however hive (and all other scripts) are expecting column name
{{DOUBLE_HIGH_VALUE}} (without the S at the end).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-4024) Derby metastore update script will fail when upgrading from 0.9.0 to 0.10.0
[
https://issues.apache.org/jira/browse/HIVE-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho reassigned HIVE-4024:
Assignee: Jarek Jarcec Cecho
Derby metastore update script will fail when upgrading from 0.9.0 to 0.10.0
---
Key: HIVE-4024
URL: https://issues.apache.org/jira/browse/HIVE-4024
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Minor
Attachments: bugHIVE-4024.patch
The problem is in following file {{011-HIVE-3649.derby.sql}} that contains
following line:
{code}
ALTER TABLE SDS ADD IS_STOREDASSUBDIRECTORIES CHAR(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Adding user jarcec to contributor list on JIRA
Awesome, thank you sir! Jarcec On Fri, Feb 15, 2013 at 08:52:29AM -0800, Ashutosh Chauhan wrote: Done. Added to contributors list. Welcome Jarcec to hive dev! Ashutosh On Fri, Feb 15, 2013 at 8:38 AM, Jarek Jarcec Cecho jar...@apache.orgwrote: Hi Hive developers, I was lately working on some small JIRAs and I'm unfortunately not able to assign those tickets to myself. As far as I know this is because I'm not in the contributor group in the Hive JIRA project configuration. Would someone with sufficient privileges add me there? This status should not grant me any additional privileges as far as know, so it should safe operation. Jarcec signature.asc Description: Digital signature
[jira] [Updated] (HIVE-4021) PostgreSQL upgrade scripts are creating column with incorrect name
[
https://issues.apache.org/jira/browse/HIVE-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4021:
-
Status: Patch Available (was: Open)
PostgreSQL upgrade scripts are creating column with incorrect name
--
Key: HIVE-4021
URL: https://issues.apache.org/jira/browse/HIVE-4021
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Assignee: Jarek Jarcec Cecho
Priority: Trivial
Attachments: bugHIVE-4021.patch
I've noticed that PostgreSQL upgrade scripts are creating table
{{PART_COL_STATS}} and {{TAB_COL_STATS}} with column {{DOUBLE_HIGH_VALUES}},
however hive (and all other scripts) are expecting column name
{{DOUBLE_HIGH_VALUE}} (without the S at the end).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-4021) PostgreSQL upgrade scripts are creating column with incorrect name
Jarek Jarcec Cecho created HIVE-4021:
Summary: PostgreSQL upgrade scripts are creating column with
incorrect name
Key: HIVE-4021
URL: https://issues.apache.org/jira/browse/HIVE-4021
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Priority: Trivial
I've noticed that PostgreSQL upgrade scripts are creating table
{{PART_COL_STATS}} and {{TAB_COL_STATS}} with column {{DOUBLE_HIGH_VALUES}},
however hive (and all other scripts) are expecting column name
{{DOUBLE_HIGH_VALUE}} (without the S at the end).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4021) PostgreSQL upgrade scripts are creating column with incorrect name
[
https://issues.apache.org/jira/browse/HIVE-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4021:
-
Attachment: bugHIVE-4021.patch
PostgreSQL upgrade scripts are creating column with incorrect name
--
Key: HIVE-4021
URL: https://issues.apache.org/jira/browse/HIVE-4021
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Priority: Trivial
Attachments: bugHIVE-4021.patch
I've noticed that PostgreSQL upgrade scripts are creating table
{{PART_COL_STATS}} and {{TAB_COL_STATS}} with column {{DOUBLE_HIGH_VALUES}},
however hive (and all other scripts) are expecting column name
{{DOUBLE_HIGH_VALUE}} (without the S at the end).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4021) PostgreSQL upgrade scripts are creating column with incorrect name
[
https://issues.apache.org/jira/browse/HIVE-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13578697#comment-13578697
]
Jarek Jarcec Cecho commented on HIVE-4021:
--
Might ask someone with sufficient privilegies to add me into the contributor
group on Jira? It seems that I still can't assign the ticket to myself.
PostgreSQL upgrade scripts are creating column with incorrect name
--
Key: HIVE-4021
URL: https://issues.apache.org/jira/browse/HIVE-4021
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Priority: Trivial
Attachments: bugHIVE-4021.patch
I've noticed that PostgreSQL upgrade scripts are creating table
{{PART_COL_STATS}} and {{TAB_COL_STATS}} with column {{DOUBLE_HIGH_VALUES}},
however hive (and all other scripts) are expecting column name
{{DOUBLE_HIGH_VALUE}} (without the S at the end).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-4024) Derby metastore update script will fail when upgrading from 0.9.0 to 0.10.0
Jarek Jarcec Cecho created HIVE-4024:
Summary: Derby metastore update script will fail when upgrading
from 0.9.0 to 0.10.0
Key: HIVE-4024
URL: https://issues.apache.org/jira/browse/HIVE-4024
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Priority: Minor
The problem is in following file {{011-HIVE-3649.derby.sql}} that contains
following line:
{code}
ALTER TABLE SDS ADD IS_STOREDASSUBDIRECTORIES CHAR(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4024) Derby metastore update script will fail when upgrading from 0.9.0 to 0.10.0
[
https://issues.apache.org/jira/browse/HIVE-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4024:
-
Attachment: bugHIVE-4024.patch
Derby metastore update script will fail when upgrading from 0.9.0 to 0.10.0
---
Key: HIVE-4024
URL: https://issues.apache.org/jira/browse/HIVE-4024
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Priority: Minor
Attachments: bugHIVE-4024.patch
The problem is in following file {{011-HIVE-3649.derby.sql}} that contains
following line:
{code}
ALTER TABLE SDS ADD IS_STOREDASSUBDIRECTORIES CHAR(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-4024) Derby metastore update script will fail when upgrading from 0.9.0 to 0.10.0
[
https://issues.apache.org/jira/browse/HIVE-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-4024:
-
Status: Patch Available (was: Open)
Derby metastore update script will fail when upgrading from 0.9.0 to 0.10.0
---
Key: HIVE-4024
URL: https://issues.apache.org/jira/browse/HIVE-4024
Project: Hive
Issue Type: Bug
Reporter: Jarek Jarcec Cecho
Priority: Minor
Attachments: bugHIVE-4024.patch
The problem is in following file {{011-HIVE-3649.derby.sql}} that contains
following line:
{code}
ALTER TABLE SDS ADD IS_STOREDASSUBDIRECTORIES CHAR(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-4007) Create abstract classes for serializer and deserializer
[ https://issues.apache.org/jira/browse/HIVE-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13575827#comment-13575827 ] Jarek Jarcec Cecho commented on HIVE-4007: -- I'm +1 on the generic idea of having abstract classes instead of interfaces for such things as Serialize/Deserialize. Abstract classes are much more flexible for maintenance and new feature addition. However changing existing code might not be easy as I'm anticipating that it will introduce backward incompatibility for all existing custom SerDes that are out there. Create abstract classes for serializer and deserializer --- Key: HIVE-4007 URL: https://issues.apache.org/jira/browse/HIVE-4007 Project: Hive Issue Type: Improvement Components: Serializers/Deserializers Reporter: Namit Jain Assignee: Namit Jain Currently, it is very difficult to change the Serializer/Deserializer interface, since all the SerDes directly implement the interface. Instead, we should have abstract classes for implementing these interfaces. In case of a interface change, only the abstract class and the relevant serde needs to change. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3995) PostgreSQL upgrade scripts are not valid
[ https://issues.apache.org/jira/browse/HIVE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated HIVE-3995: - Attachment: postgre_update_issue.patch Attaching updated patch including Mark's notes from review board. PostgreSQL upgrade scripts are not valid Key: HIVE-3995 URL: https://issues.apache.org/jira/browse/HIVE-3995 Project: Hive Issue Type: Bug Components: Metastore Reporter: Jarek Jarcec Cecho Attachments: postgre_update_issue.patch, postgre_update_issue.patch I've noticed that scripts for upgrading metastore backed up on PostgreSQL are not valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3998) Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
Jarek Jarcec Cecho created HIVE-3998:
Summary: Oracle metastore update script will fail when upgrading
from 0.9.0 to 0.10.0
Key: HIVE-3998
URL: https://issues.apache.org/jira/browse/HIVE-3998
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
The problem is in following file {{011-HIVE-3649.oracle.sql}} that contains
following line:
{code}
alter table SDS add IS_STOREDASSUBDIRECTORIES NUMBER(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one column.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3998) Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
[
https://issues.apache.org/jira/browse/HIVE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-3998:
-
Attachment: oracle_update_issue.patch
Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
Key: HIVE-3998
URL: https://issues.apache.org/jira/browse/HIVE-3998
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
Attachments: oracle_update_issue.patch
The problem is in following file {{011-HIVE-3649.oracle.sql}} that contains
following line:
{code}
alter table SDS add IS_STOREDASSUBDIRECTORIES NUMBER(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one column.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3998) Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
[
https://issues.apache.org/jira/browse/HIVE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-3998:
-
Status: Patch Available (was: Open)
Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
Key: HIVE-3998
URL: https://issues.apache.org/jira/browse/HIVE-3998
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
Attachments: oracle_update_issue.patch
The problem is in following file {{011-HIVE-3649.oracle.sql}} that contains
following line:
{code}
alter table SDS add IS_STOREDASSUBDIRECTORIES NUMBER(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one column.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3998) Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
[
https://issues.apache.org/jira/browse/HIVE-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-3998:
-
Description:
The problem is in following file {{011-HIVE-3649.oracle.sql}} that contains
following line:
{code}
alter table SDS add IS_STOREDASSUBDIRECTORIES NUMBER(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one row.
was:
The problem is in following file {{011-HIVE-3649.oracle.sql}} that contains
following line:
{code}
alter table SDS add IS_STOREDASSUBDIRECTORIES NUMBER(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one column.
Oracle metastore update script will fail when upgrading from 0.9.0 to 0.10.0
Key: HIVE-3998
URL: https://issues.apache.org/jira/browse/HIVE-3998
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
Attachments: oracle_update_issue.patch
The problem is in following file {{011-HIVE-3649.oracle.sql}} that contains
following line:
{code}
alter table SDS add IS_STOREDASSUBDIRECTORIES NUMBER(1) NOT NULL;
{code}
This query will however fail if the table SDS have at least one row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load
Jarek Jarcec Cecho created HIVE-3999:
Summary: Mysql metastore upgrade script will end up with different
schema than the full schema load
Key: HIVE-3999
URL: https://issues.apache.org/jira/browse/HIVE-3999
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
I've noticed that the file {{hive-schema-0.10.0.mysql.sql}} is creating table
SDS with following column:
{code}
`IS_STOREDASSUBDIRECTORIES` bit(1) NOT NULL,
{code}
However the upgrade script {{011-HIVE-3649.mysql.sql}} will create the column
differently:
{code}
ALTER TABLE `SDS` ADD `IS_STOREDASSUBDIRECTORIES` bit(1) ;
{code}
Thus user will get slightly different schema each time - once with NOT NULL
and secondly with NULL definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load
[
https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-3999:
-
Attachment: mysql_upgrade_issue.patch
Mysql metastore upgrade script will end up with different schema than the
full schema load
--
Key: HIVE-3999
URL: https://issues.apache.org/jira/browse/HIVE-3999
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
Attachments: mysql_upgrade_issue.patch
I've noticed that the file {{hive-schema-0.10.0.mysql.sql}} is creating table
SDS with following column:
{code}
`IS_STOREDASSUBDIRECTORIES` bit(1) NOT NULL,
{code}
However the upgrade script {{011-HIVE-3649.mysql.sql}} will create the column
differently:
{code}
ALTER TABLE `SDS` ADD `IS_STOREDASSUBDIRECTORIES` bit(1) ;
{code}
Thus user will get slightly different schema each time - once with NOT NULL
and secondly with NULL definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3999) Mysql metastore upgrade script will end up with different schema than the full schema load
[
https://issues.apache.org/jira/browse/HIVE-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated HIVE-3999:
-
Status: Patch Available (was: Open)
Mysql metastore upgrade script will end up with different schema than the
full schema load
--
Key: HIVE-3999
URL: https://issues.apache.org/jira/browse/HIVE-3999
Project: Hive
Issue Type: Bug
Components: Metastore
Reporter: Jarek Jarcec Cecho
Attachments: mysql_upgrade_issue.patch
I've noticed that the file {{hive-schema-0.10.0.mysql.sql}} is creating table
SDS with following column:
{code}
`IS_STOREDASSUBDIRECTORIES` bit(1) NOT NULL,
{code}
However the upgrade script {{011-HIVE-3649.mysql.sql}} will create the column
differently:
{code}
ALTER TABLE `SDS` ADD `IS_STOREDASSUBDIRECTORIES` bit(1) ;
{code}
Thus user will get slightly different schema each time - once with NOT NULL
and secondly with NULL definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-3994) Hive metastore is not working on PostgreSQL 9.2 (most likely on anything 9.0+)
[
https://issues.apache.org/jira/browse/HIVE-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho resolved HIVE-3994.
--
Resolution: Not A Problem
Och thank you Shreepadma!
I've reconfigured my PostgreSQL 9.2 by turning standard_conforming_string
property to off and hive metastore is working correctly again!
I'm closing this issue as not a problem.
Jarcec
Hive metastore is not working on PostgreSQL 9.2 (most likely on anything 9.0+)
--
Key: HIVE-3994
URL: https://issues.apache.org/jira/browse/HIVE-3994
Project: Hive
Issue Type: Improvement
Reporter: Jarek Jarcec Cecho
I'm getting following exception when running metastore on PostgreSQL 9.2:
{code}
Caused by: javax.jdo.JDODataStoreException: Error executing JDOQL query
SELECT THIS.TBL_NAME AS NUCORDER0 FROM TBLS THIS LEFT OUTER JOIN
DBS THIS_DATABASE_NAME ON THIS.DB_ID = THIS_DATABASE_NAME.DB_ID
WHERE THIS_DATABASE_NAME.NAME = ? AND (LOWER(THIS.TBL_NAME) LIKE ?
ESCAPE '\\' ) ORDER BY NUCORDER0 : ERROR: invalid escape string
Hint: Escape string must be empty or one character..
NestedThrowables:
org.postgresql.util.PSQLException: ERROR: invalid escape string
Hint: Escape string must be empty or one character.
at
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:313)
at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:252)
at
org.apache.hadoop.hive.metastore.ObjectStore.getTables(ObjectStore.java:759)
... 28 more
Caused by: org.postgresql.util.PSQLException: ERROR: invalid escape string
Hint: Escape string must be empty or one character.
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2096)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1829)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:510)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:386)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:271)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.datanucleus.store.rdbms.SQLController.executeStatementQuery(SQLController.java:457)
at
org.datanucleus.store.rdbms.query.legacy.SQLEvaluator.evaluate(SQLEvaluator.java:123)
at
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.performExecute(JDOQLQuery.java:288)
at org.datanucleus.store.query.Query.executeQuery(Query.java:1657)
at
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.executeQuery(JDOQLQuery.java:245)
at org.datanucleus.store.query.Query.executeWithArray(Query.java:1499)
at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:243)
... 29 more
{code}
I've google a bit about that and I found a lot of similar issues in different
projects thus I'm assuming that this might be some backward compatibility
issue on PostgreSQL side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3994) Hive metastore is not working on PostgreSQL 9.2 (most likely on anything 9.0+)
Jarek Jarcec Cecho created HIVE-3994:
Summary: Hive metastore is not working on PostgreSQL 9.2 (most
likely on anything 9.0+)
Key: HIVE-3994
URL: https://issues.apache.org/jira/browse/HIVE-3994
Project: Hive
Issue Type: Improvement
Reporter: Jarek Jarcec Cecho
I'm getting following exception when running metastore on PostgreSQL 9.2:
{code}
Caused by: javax.jdo.JDODataStoreException: Error executing JDOQL query SELECT
THIS.TBL_NAME AS NUCORDER0 FROM TBLS THIS LEFT OUTER JOIN DBS
THIS_DATABASE_NAME ON THIS.DB_ID = THIS_DATABASE_NAME.DB_ID WHERE
THIS_DATABASE_NAME.NAME = ? AND (LOWER(THIS.TBL_NAME) LIKE ? ESCAPE
'\\' ) ORDER BY NUCORDER0 : ERROR: invalid escape string
Hint: Escape string must be empty or one character..
NestedThrowables:
org.postgresql.util.PSQLException: ERROR: invalid escape string
Hint: Escape string must be empty or one character.
at
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:313)
at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:252)
at
org.apache.hadoop.hive.metastore.ObjectStore.getTables(ObjectStore.java:759)
... 28 more
Caused by: org.postgresql.util.PSQLException: ERROR: invalid escape string
Hint: Escape string must be empty or one character.
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2096)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1829)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:510)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:386)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:271)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.datanucleus.store.rdbms.SQLController.executeStatementQuery(SQLController.java:457)
at
org.datanucleus.store.rdbms.query.legacy.SQLEvaluator.evaluate(SQLEvaluator.java:123)
at
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.performExecute(JDOQLQuery.java:288)
at org.datanucleus.store.query.Query.executeQuery(Query.java:1657)
at
org.datanucleus.store.rdbms.query.legacy.JDOQLQuery.executeQuery(JDOQLQuery.java:245)
at org.datanucleus.store.query.Query.executeWithArray(Query.java:1499)
at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:243)
... 29 more
{code}
I've google a bit about that and I found a lot of similar issues in different
projects thus I'm assuming that this might be some backward compatibility issue
on PostgreSQL side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-3995) PostgreSQL upgrade scripts are not valid
Jarek Jarcec Cecho created HIVE-3995: Summary: PostgreSQL upgrade scripts are not valid Key: HIVE-3995 URL: https://issues.apache.org/jira/browse/HIVE-3995 Project: Hive Issue Type: Bug Components: Metastore Reporter: Jarek Jarcec Cecho I've noticed that scripts for upgrading metastore backed up on PostgreSQL are not valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3995) PostgreSQL upgrade scripts are not valid
[ https://issues.apache.org/jira/browse/HIVE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated HIVE-3995: - Attachment: postgre_update_issue.patch PostgreSQL upgrade scripts are not valid Key: HIVE-3995 URL: https://issues.apache.org/jira/browse/HIVE-3995 Project: Hive Issue Type: Bug Components: Metastore Reporter: Jarek Jarcec Cecho Attachments: postgre_update_issue.patch I've noticed that scripts for upgrading metastore backed up on PostgreSQL are not valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3995) PostgreSQL upgrade scripts are not valid
[ https://issues.apache.org/jira/browse/HIVE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated HIVE-3995: - Status: Patch Available (was: Open) PostgreSQL upgrade scripts are not valid Key: HIVE-3995 URL: https://issues.apache.org/jira/browse/HIVE-3995 Project: Hive Issue Type: Bug Components: Metastore Reporter: Jarek Jarcec Cecho Attachments: postgre_update_issue.patch I've noticed that scripts for upgrading metastore backed up on PostgreSQL are not valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3995) PostgreSQL upgrade scripts are not valid
[ https://issues.apache.org/jira/browse/HIVE-3995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13573103#comment-13573103 ] Jarek Jarcec Cecho commented on HIVE-3995: -- I'm attaching patch that is fixing the upgrade scripts. I've tried to assign the jira to myself but it seems that I'm not in the contributor group in the jira. Might I ask someone to add me? PostgreSQL upgrade scripts are not valid Key: HIVE-3995 URL: https://issues.apache.org/jira/browse/HIVE-3995 Project: Hive Issue Type: Bug Components: Metastore Reporter: Jarek Jarcec Cecho Attachments: postgre_update_issue.patch I've noticed that scripts for upgrading metastore backed up on PostgreSQL are not valid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Amend Hive Bylaws + Add HCatalog Submodule
Measure 1: +1 (non binding) Measure 2: +1 (non binding) Jarcec On Mon, Jan 28, 2013 at 07:00:14PM -0600, Brock Noland wrote: +1 and +1 (non-binding) On Mon, Jan 28, 2013 at 5:09 PM, Owen O'Malley omal...@apache.org wrote: +1 and +1 On Mon, Jan 28, 2013 at 1:56 PM, Ashish Thusoo athu...@qubole.com wrote: Measure 1: +1 Measure 2: +1 Ashish On Mon, Jan 28, 2013 at 1:11 PM, Ashutosh Chauhan hashut...@apache.org wrote: Measure 1: +1 Measure 2: +1 Ashutosh On Mon, Jan 28, 2013 at 11:48 AM, Carl Steinbach c...@apache.org wrote: Measure 1: +1 (binding) Measure 2: +1 (binding) On Mon, Jan 28, 2013 at 11:47 AM, Carl Steinbach c...@apache.org wrote: I am calling a vote on the following two measures. Measure 1: Amend Hive Bylaws to Define Submodules and Submodule Committers If this measure passes the Apache Hive Project Bylaws will be amended with the following changes: https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hive+Bylaws+for+Submodule+Committers The motivation for these changes is discussed in the following email thread which appeared on the hive-dev and hcatalog-dev mailing lists: http://markmail.org/thread/u5nap7ghvyo7euqa Measure 2: Create HCatalog Submodule and Adopt HCatalog Codebase This measure provides for 1) the establishment of an HCatalog submodule in the Apache Hive Project, 2) the adoption of the Apache HCatalog codebase into the Hive HCatalog submodule, and 3) adding all currently active HCatalog committers as submodule committers on the Hive HCatalog submodule. Passage of this measure depends on the passage of Measure 1. Voting: Both measures require +1 votes from 2/3 of active Hive PMC members in order to pass. All participants in the Hive project are encouraged to vote on these measures, but only votes from active Hive PMC members are binding. The voting period commences immediately and shall last a minimum of six days. Voting is carried out by replying to this email thread. You must indicate which measure you are voting on in order for your vote to be counted. More details about the voting process can be found in the Apache Hive Project Bylaws: https://cwiki.apache.org/confluence/display/Hive/Bylaws -- Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/ signature.asc Description: Digital signature
