[jira] [Updated] (HIVE-3030) escape more chars for script operator
[ https://issues.apache.org/jira/browse/HIVE-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3030: - Status: Patch Available (was: Open) escape more chars for script operator - Key: HIVE-3030 URL: https://issues.apache.org/jira/browse/HIVE-3030 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain Only new line was being escaped. The same behavior needs to be done for carriage returns, and tabs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3030) escape more chars for script operator
[ https://issues.apache.org/jira/browse/HIVE-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276505#comment-13276505 ] Namit Jain commented on HIVE-3030: -- https://reviews.facebook.net/D3261 escape more chars for script operator - Key: HIVE-3030 URL: https://issues.apache.org/jira/browse/HIVE-3030 Project: Hive Issue Type: Bug Reporter: Namit Jain Assignee: Namit Jain Only new line was being escaped. The same behavior needs to be done for carriage returns, and tabs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2539) Enable passing username/password via JDBC
[ https://issues.apache.org/jira/browse/HIVE-2539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276529#comment-13276529 ] Mac Fang commented on HIVE-2539: our solution is enable the login in the thrift RPC and use login when initialize the HiveConnection. Then in HiveServer, we put the username into the SessionState after authentication. Enable passing username/password via JDBC - Key: HIVE-2539 URL: https://issues.apache.org/jira/browse/HIVE-2539 Project: Hive Issue Type: Improvement Components: JDBC Affects Versions: 0.7.1 Reporter: Sriram Krishnan Assignee: chunqing xie Labels: patch Attachments: HIVE-2539.PATCH Changing the username and/or the password seems to have no effect (also confirmed here: https://cwiki.apache.org/Hive/hivejdbcinterface.html). Connection con = DriverManager.getConnection(jdbc:hive://localhost:1/default, , ); Would be beneficial to pass the username/password via JDBC - and also for the server to honor the username password being passed (may be dependent of that being fixed first). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3016) Allow disabling foreign table access (cross database) using hiveconf
[
https://issues.apache.org/jira/browse/HIVE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276545#comment-13276545
]
Carl Steinbach commented on HIVE-3016:
--
@Namit: I found this in authorization_5.q in the clientpositive directory:
{noformat}
GRANT drop ON DATABASE test_db TO USER hive_test_user;
GRANT select ON DATABASE test_db TO USER hive_test_user;
SHOW GRANT USER hive_test_user ON DATABASE test_db;
CREATE ROLE db_test_role;
GRANT ROLE db_test_role TO USER hive_test_user;
SHOW ROLE GRANT USER hive_test_user;
GRANT drop ON DATABASE test_db TO ROLE db_test_role;
GRANT select ON DATABASE test_db TO ROLE db_test_role;
SHOW GRANT ROLE db_test_role ON DATABASE test_db;
{noformat}
Looks like this patch duplicates functionality that is already provided by the
authorization system.
Allow disabling foreign table access (cross database) using hiveconf
Key: HIVE-3016
URL: https://issues.apache.org/jira/browse/HIVE-3016
Project: Hive
Issue Type: Improvement
Components: Query Processor
Reporter: Sambavi Muthukrishnan
Assignee: Sambavi Muthukrishnan
Priority: Minor
Attachments: hive-3016.1.patch.txt
Original Estimate: 48h
Remaining Estimate: 48h
Disallow cross database access to tables using Y.T syntax under a specific
configuration in HiveConf.
i.e. when hive.error.on.crossdatabaseaccess is set to true, return an error
when Y.T syntax is used to access tables and Y is not the current database.
This can be set both via the client and in hive-site.xml, and will default to
false.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3030) escape more chars for script operator
[ https://issues.apache.org/jira/browse/HIVE-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3030: - Status: Open (was: Patch Available) @Namit: I added some comments on phabricator. Is it possible to have phabricator copy the comments to JIRA? Do we know why this stopped working? If this keeps happening I think we need to revert back to RB since having a permanent record on JIRA is a requirement. escape more chars for script operator - Key: HIVE-3030 URL: https://issues.apache.org/jira/browse/HIVE-3030 Project: Hive Issue Type: Bug Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Only new line was being escaped. The same behavior needs to be done for carriage returns, and tabs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3030) escape more chars for script operator
[ https://issues.apache.org/jira/browse/HIVE-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3030: - Component/s: Query Processor escape more chars for script operator - Key: HIVE-3030 URL: https://issues.apache.org/jira/browse/HIVE-3030 Project: Hive Issue Type: Bug Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Only new line was being escaped. The same behavior needs to be done for carriage returns, and tabs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1719) Move RegexSerDe out of hive-contrib and over to hive-serde
[
https://issues.apache.org/jira/browse/HIVE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276587#comment-13276587
]
Phabricator commented on HIVE-1719:
---
cwsteinbach has requested changes to the revision HIVE-1719 [jira] Move
RegexSerDe out of hive-contrib and over to hive-serde.
INLINE COMMENTS
serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java:45 Please remove
It can also serialize the row object using a format string.
serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java:42 Please change
to RegexSerDe uses a regular expression to deserialize row data. It does not
support data serialization.
serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java:93 Please remove
the outputFormatString variable and just do:
if (null != tbl.getProperty(output.format.string)) {
LOG.warn();
}
serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java:102 Throw the
exception here instead of in the next IF block.
serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java:186 if
(!alreadyLoggedNoMatch) {
...
}
serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java:158 Adding
Count to the end of this variable name would help to make it clear that this
is a scalar variable as opposed to a collection type.
serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java:184 Does this
logic do anything? It looks like the code will log the first unmatched row it
finds, set alreadyLoggedNoMatch = true, and subsequently never log another
warning. Is there any reason to call getNextNumberToDisplay()?
serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java:205 I think it's
fine to log one warning for the first row that has partial matches. No need to
get fancy with this exponential backoff logging strategy.
REVISION DETAIL
https://reviews.facebook.net/D3249
BRANCH
HIVE-1719-trunk
To: JIRA, cwsteinbach, shreepadma
Move RegexSerDe out of hive-contrib and over to hive-serde
--
Key: HIVE-1719
URL: https://issues.apache.org/jira/browse/HIVE-1719
Project: Hive
Issue Type: Task
Components: Serializers/Deserializers
Reporter: Carl Steinbach
Assignee: Shreepadma Venugopalan
Attachments: HIVE-1719.3.patch.txt, HIVE-1719.D3051.1.patch,
HIVE-1719.D3051.2.patch, HIVE-1719.D3141.1.patch, HIVE-1719.D3249.1.patch,
HIVE-1719.D3249.1.patch, HIVE-1719.patch
RegexSerDe is as much a part of the standard Hive distribution as the other
SerDes
currently in hive-serde. I think we should move it over to the hive-serde
module so that
users don't have to go to the added effort of manually registering the
contrib jar before
using it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3029) Update ShimLoader to work with Hadoop 2.x
[ https://issues.apache.org/jira/browse/HIVE-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3029: - Status: Patch Available (was: Open) Update ShimLoader to work with Hadoop 2.x - Key: HIVE-3029 URL: https://issues.apache.org/jira/browse/HIVE-3029 Project: Hive Issue Type: Bug Components: Shims Reporter: Carl Steinbach Assignee: Carl Steinbach Attachments: HIVE-3029.D3255.1.patch, HIVE-3029.D3255.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3029) Update ShimLoader to work with Hadoop 2.x
[ https://issues.apache.org/jira/browse/HIVE-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Steinbach updated HIVE-3029: - Attachment: HIVE-3029.D3255.1.patch Update ShimLoader to work with Hadoop 2.x - Key: HIVE-3029 URL: https://issues.apache.org/jira/browse/HIVE-3029 Project: Hive Issue Type: Bug Components: Shims Reporter: Carl Steinbach Assignee: Carl Steinbach Attachments: HIVE-3029.D3255.1.patch, HIVE-3029.D3255.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2821) union with two mapjoin will throw NPE
[
https://issues.apache.org/jira/browse/HIVE-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276606#comment-13276606
]
Zhang Xinyu commented on HIVE-2821:
---
hive explain select count(1) from (
select key,value from (select /*+ MAPJOIN(b) */ a.key, a.value from src a
join src1 b on a.key=b.key) t1
union all
select key,value from (select /*+ MAPJOIN(bb) */ aa.key, aa.value from
src aa join src1 bb on aa.key=bb.key) t2
) t3;
FAILED: Hive Internal Error: java.lang.NullPointerException(null)
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.optimizer.ppr.PartitionPruner.prune(PartitionPruner.java:170)
at
org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.setTaskPlan(GenMapRedUtils.java:553)
at
org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.setTaskPlan(GenMapRedUtils.java:514)
at
org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.initPlan(GenMapRedUtils.java:125)
at
org.apache.hadoop.hive.ql.optimizer.GenMRRedSink1.process(GenMRRedSink1.java:76)
at
org.apache.hadoop.hive.ql.optimizer.GenMRRedSink3.process(GenMRRedSink3.java:64)
at
org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:89)
...
environment: hive-05b8af0(0.8.1release); Mac 10.7.3; java
1.6.0_31-b04-415-11M3635.
I debug in eclipse to see how to generate mapjoin plan, find current logic
depends on the sequence walk each TableScanOperator.
For case like:
TS_1 - \
TS_2 - Mapjoin_3 - \
TS_4 - Mapjoin_5
must walk TS_1 or TS_2 first, or hive will throw NPE;
For case like:
TS_1 - \
TS_2 - Mapjoin_3 - Union_4 - \
.TS_5 - Mapjoin_6
must walk TS_5 first, or throw NPE;
What i do is to replace private HashMapString, Operator? extends
Serializable topOps;(in SemanticAnalyzer.java) with private
LinkedHashMapString, Operator? extends Serializable topOps; and hack a
Transform in Optimizer.java to adjust the sequence of each TSOperator. I
tested, it works well.
But that is not enough for case like Mapjoin union all Mapjoin(map only union)
then followed by a reducer. I have another hack, in
ql/src/java/org/apache/hadoop/hive/ql/optimizer/GenMapRedUtils.java:
123c123
if (!seenOps.contains(currTopOp)) {
---
if (!seenOps.contains(currTopOp) currTopOp!=null) {
It's too hack, and not even tested by running job(its plan from explain is
OK). I'm waiting for official patch too.
union with two mapjoin will throw NPE
---
Key: HIVE-2821
URL: https://issues.apache.org/jira/browse/HIVE-2821
Project: Hive
Issue Type: Bug
Affects Versions: 0.7.0
Environment: Linux zongren-VirtualBox 3.0.0-14-generic #23-Ubuntu SMP
Mon Nov 21 20:34:47 UTC 2011 i686 i686 i386 GNU/Linux
java version 1.6.0_25
hadoop-0.20.2-cdh3u0
hive-0.7.0-cdh3u0
Reporter: caofangkun
Priority: Critical
Labels: optimizer, ql, union
create table src (key string, value string);
create table src1 (key string, value string);
select count(*) from (
select /+mapjoin(b)/ a.*
from src a
join
src1 b
on a.key=b.key
where a.key=48
union all
select /+mapjoin(bb)/ aa.*
from src aa
join
src1 bb
on aa.key=bb.key
where aa.key=100
) t;
FAILED: Hive Internal Error: java.lang.NullPointerException(null)
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.optimizer.ppr.PartitionPruner.prune(PartitionPruner.java:156)
at
org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.setTaskPlan(GenMapRedUtils.java:553)
at
org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.setTaskPlan(GenMapRedUtils.java:514)
at
org.apache.hadoop.hive.ql.optimizer.GenMapRedUtils.initPlan(GenMapRedUtils.java:125)
at
org.apache.hadoop.hive.ql.optimizer.GenMRRedSink1.process(GenMRRedSink1.java:76)
at
org.apache.hadoop.hive.ql.optimizer.GenMRRedSink3.process(GenMRRedSink3.java:64)
at
org.apache.hadoop.hive.ql.lib.DefaultRuleDispatcher.dispatch(DefaultRuleDispatcher.java:89)
at
org.apache.hadoop.hive.ql.lib.DefaultGraphWalker.dispatch(DefaultGraphWalker.java:88)
at
org.apache.hadoop.hive.ql.parse.GenMapRedWalker.walk(GenMapRedWalker.java:55)
at
org.apache.hadoop.hive.ql.parse.GenMapRedWalker.walk(GenMapRedWalker.java:67)
at
org.apache.hadoop.hive.ql.parse.GenMapRedWalker.walk(GenMapRedWalker.java:67)
at
org.apache.hadoop.hive.ql.parse.GenMapRedWalker.walk(GenMapRedWalker.java:67)
at
org.apache.hadoop.hive.ql.parse.GenMapRedWalker.walk(GenMapRedWalker.java:67)
at
org.apache.hadoop.hive.ql.parse.GenMapRedWalker.walk(GenMapRedWalker.java:67)
at
org.apache.hadoop.hive.ql.parse.GenMapRedWalker.walk(GenMapRedWalker.java:67)
at
org.apache.hadoop.hive.ql.parse.GenMapRedWalker.walk(GenMapRedWalker.java:67)
at
[jira] [Commented] (HIVE-2757) hive can't find hadoop executor scripts without HADOOP_HOME set
[ https://issues.apache.org/jira/browse/HIVE-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276645#comment-13276645 ] Hudson commented on HIVE-2757: -- Integrated in Hive-trunk-h0.21 #1434 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1434/]) HIVE-3014 [jira] Fix metastore test failures caused by HIVE-2757 (Zhenxiao Luo via Carl Steinbach) Summary: HIVE-3014: Fix metastore test failures caused by HIVE-2757 Test Plan: EMPTY Reviewers: JIRA, cwsteinbach Reviewed By: cwsteinbach Differential Revision: https://reviews.facebook.net/D3213 (Revision 1339004) Result = SUCCESS cws : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1339004 Files : * /hive/trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java hive can't find hadoop executor scripts without HADOOP_HOME set --- Key: HIVE-2757 URL: https://issues.apache.org/jira/browse/HIVE-2757 Project: Hive Issue Type: Bug Components: CLI Affects Versions: 0.8.0 Reporter: Roman Shaposhnik Assignee: Roman Shaposhnik Fix For: 0.10.0 Attachments: HIVE-2757-2.patch.txt, HIVE-2757.D3075.1.patch, HIVE-2757.patch.txt, HIVE-2757.patch.txt, hive-2757.diff The trouble is that in Hadoop 0.23 HADOOP_HOME has been deprecated. I think it would be really nice if bin/hive can be modified to capture the which hadoop and pass that as a property into the JVM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3014) Fix metastore test failures caused by HIVE-2757
[ https://issues.apache.org/jira/browse/HIVE-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276644#comment-13276644 ] Hudson commented on HIVE-3014: -- Integrated in Hive-trunk-h0.21 #1434 (See [https://builds.apache.org/job/Hive-trunk-h0.21/1434/]) HIVE-3014 [jira] Fix metastore test failures caused by HIVE-2757 (Zhenxiao Luo via Carl Steinbach) Summary: HIVE-3014: Fix metastore test failures caused by HIVE-2757 Test Plan: EMPTY Reviewers: JIRA, cwsteinbach Reviewed By: cwsteinbach Differential Revision: https://reviews.facebook.net/D3213 (Revision 1339004) Result = SUCCESS cws : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1339004 Files : * /hive/trunk/common/src/java/org/apache/hadoop/hive/conf/HiveConf.java Fix metastore test failures caused by HIVE-2757 --- Key: HIVE-3014 URL: https://issues.apache.org/jira/browse/HIVE-3014 Project: Hive Issue Type: Bug Components: Metastore Reporter: Carl Steinbach Assignee: Zhenxiao Luo Fix For: 0.10.0 Attachments: HIVE-3014.1.patch.txt, HIVE-3014.D3213.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Hive-trunk-h0.21 - Build # 1434 - Fixed
Changes for Build #1422 Changes for Build #1423 [cws] HIVE-2979. Implement INCLUDE_HADOOP_MAJOR_VERSION test macro (Zhenxiao Luo via cws) [cws] HIVE-2757. Hive can't find hadoop executor scripts without HADOOP_HOME set (Roman Shaposhnik via cws) Changes for Build #1424 [kevinwilfong] HIVE-3012 hive custom scripts do not work well if the data contains new lines (njain via kevinwilfong) Changes for Build #1425 Changes for Build #1426 Changes for Build #1427 Changes for Build #1428 [namit] HIVE-3018 Make the new header for RC Files introduced in HIVE-2711 optional (Kevin Wilfong via namit) Changes for Build #1429 Changes for Build #1430 [namit] HIVE-3022 Add hive.exec.rcfile.use.explicit.header to hive-default.xml.template (Kevin Wilfong via namit) Changes for Build #1431 [namit] HIVE-3001 Returning Meaningful Error Codes Messages (Bhushan Mandhani via namit) Changes for Build #1432 Changes for Build #1433 [namit] HIVE-2732 Reduce Sink deduplication fails if the child reduce sink is followed by a join (Navis via namit) Changes for Build #1434 [cws] HIVE-3014 [jira] Fix metastore test failures caused by HIVE-2757 (Zhenxiao Luo via Carl Steinbach) Summary: HIVE-3014: Fix metastore test failures caused by HIVE-2757 Test Plan: EMPTY Reviewers: JIRA, cwsteinbach Reviewed By: cwsteinbach Differential Revision: https://reviews.facebook.net/D3213 All tests passed The Apache Jenkins build system has built Hive-trunk-h0.21 (build #1434) Status: Fixed Check console output at https://builds.apache.org/job/Hive-trunk-h0.21/1434/ to view the results.
[jira] [Commented] (HIVE-1065) When data is large,a reducer's memory can not hold the big data by using list to store the data, and get an error out of memory
[ https://issues.apache.org/jira/browse/HIVE-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276691#comment-13276691 ] ransom.hezhiqiang commented on HIVE-1065: - MapJoin,bucket mapJoin,sorted bucket MapJoin. and also can used Stream table to steam the big table. if two table's data is also very large . try skew join. change the tasknum. When data is large,a reducer's memory can not hold the big data by using list to store the data, and get an error out of memory - Key: HIVE-1065 URL: https://issues.apache.org/jira/browse/HIVE-1065 Project: Hive Issue Type: Bug Affects Versions: 0.3.0 Environment: redhat enterprise 4.0 Reporter: fuyangchang Priority: Critical Original Estimate: 168h Remaining Estimate: 168h When data is large,I do a join operation ,a reducer's memory can not hold the big data by using list to store the data, and get an error out of memory -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-1719) Move RegexSerDe out of hive-contrib and over to hive-serde
[ https://issues.apache.org/jira/browse/HIVE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-1719: -- Attachment: HIVE-1719.D3249.2.patch shreepadma updated the revision HIVE-1719 [jira] Move RegexSerDe out of hive-contrib and over to hive-serde. Reviewers: JIRA, cwsteinbach Regex Serde Changes RegexSerDe is as much a part of the standard Hive distribution as the other SerDes currently in hive-serde. I think we should move it over to the hive-serde module so that users don't have to go to the added effort of manually registering the contrib jar before using it. This includes the changes requested by Carl from the previous revision. REVISION DETAIL https://reviews.facebook.net/D3249 AFFECTED FILES contrib/src/test/queries/clientnegative/serde_regex.q contrib/src/test/queries/clientpositive/serde_regex.q contrib/src/test/results/clientnegative/serde_regex.q.out contrib/src/test/results/clientpositive/serde_regex.q.out ql/src/test/queries/clientnegative/serde_regex.q ql/src/test/queries/clientnegative/serde_regex2.q ql/src/test/queries/clientnegative/serde_regex3.q ql/src/test/queries/clientpositive/serde_regex.q ql/src/test/results/clientnegative/serde_regex.q.out ql/src/test/results/clientnegative/serde_regex2.q.out ql/src/test/results/clientnegative/serde_regex3.q.out ql/src/test/results/clientpositive/serde_regex.q.out serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java To: JIRA, cwsteinbach, shreepadma Move RegexSerDe out of hive-contrib and over to hive-serde -- Key: HIVE-1719 URL: https://issues.apache.org/jira/browse/HIVE-1719 Project: Hive Issue Type: Task Components: Serializers/Deserializers Reporter: Carl Steinbach Assignee: Shreepadma Venugopalan Attachments: HIVE-1719.3.patch.txt, HIVE-1719.D3051.1.patch, HIVE-1719.D3051.2.patch, HIVE-1719.D3141.1.patch, HIVE-1719.D3249.1.patch, HIVE-1719.D3249.1.patch, HIVE-1719.D3249.2.patch, HIVE-1719.patch RegexSerDe is as much a part of the standard Hive distribution as the other SerDes currently in hive-serde. I think we should move it over to the hive-serde module so that users don't have to go to the added effort of manually registering the contrib jar before using it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Build failed in Jenkins: Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false #18
See https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/ -- [...truncated 5309 lines...] [echo] Project: anttasks create-dirs: [echo] Project: shims [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/shims [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/shims/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/shims/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/shims/test/src [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/shims/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/shims/test/resources [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/ws/hive/shims/src/test/resources does not exist. init: [echo] Project: shims create-dirs: [echo] Project: common [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/common [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/common/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/common/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/common/test/src [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/common/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/common/test/resources [copy] Copying 2 files to https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/common/test/resources init: [echo] Project: common create-dirs: [echo] Project: serde [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/serde [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/serde/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/serde/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/serde/test/src [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/serde/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/serde/test/resources [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/ws/hive/serde/src/test/resources does not exist. init: [echo] Project: serde create-dirs: [echo] Project: metastore [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/metastore [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/metastore/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/metastore/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/metastore/test/src [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/metastore/test/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/metastore/test/resources [copy] Warning: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/ws/hive/metastore/src/test/resources does not exist. init: [echo] Project: metastore create-dirs: [echo] Project: ql [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/ql [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/ql/classes [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/ql/test [mkdir] Created dir: https://builds.apache.org/job/Hive-0.9.1-SNAPSHOT-h0.21-keepgoing=false/18/artifact/hive/build/ql/test/src [mkdir] Created dir:
[jira] [Updated] (HIVE-1719) Move RegexSerDe out of hive-contrib and over to hive-serde
[ https://issues.apache.org/jira/browse/HIVE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phabricator updated HIVE-1719: -- Attachment: HIVE-1719.D3249.3.patch shreepadma updated the revision HIVE-1719 [jira] Move RegexSerDe out of hive-contrib and over to hive-serde. Reviewers: JIRA, cwsteinbach - HIVE-1719: Changes requested by Carl REVISION DETAIL https://reviews.facebook.net/D3249 AFFECTED FILES contrib/src/test/queries/clientnegative/serde_regex.q contrib/src/test/queries/clientpositive/serde_regex.q contrib/src/test/results/clientnegative/serde_regex.q.out contrib/src/test/results/clientpositive/serde_regex.q.out ql/src/test/queries/clientnegative/serde_regex.q ql/src/test/queries/clientnegative/serde_regex2.q ql/src/test/queries/clientnegative/serde_regex3.q ql/src/test/queries/clientpositive/serde_regex.q ql/src/test/results/clientnegative/serde_regex.q.out ql/src/test/results/clientnegative/serde_regex2.q.out ql/src/test/results/clientnegative/serde_regex3.q.out ql/src/test/results/clientpositive/serde_regex.q.out serde/src/java/org/apache/hadoop/hive/serde2/RegexSerDe.java To: JIRA, cwsteinbach, shreepadma Move RegexSerDe out of hive-contrib and over to hive-serde -- Key: HIVE-1719 URL: https://issues.apache.org/jira/browse/HIVE-1719 Project: Hive Issue Type: Task Components: Serializers/Deserializers Reporter: Carl Steinbach Assignee: Shreepadma Venugopalan Attachments: HIVE-1719.3.patch.txt, HIVE-1719.D3051.1.patch, HIVE-1719.D3051.2.patch, HIVE-1719.D3141.1.patch, HIVE-1719.D3249.1.patch, HIVE-1719.D3249.1.patch, HIVE-1719.D3249.2.patch, HIVE-1719.D3249.3.patch, HIVE-1719.patch RegexSerDe is as much a part of the standard Hive distribution as the other SerDes currently in hive-serde. I think we should move it over to the hive-serde module so that users don't have to go to the added effort of manually registering the contrib jar before using it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3016) Allow disabling foreign table access (cross database) using hiveconf
[ https://issues.apache.org/jira/browse/HIVE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276913#comment-13276913 ] Sambavi Muthukrishnan commented on HIVE-3016: - Carl: we are only trying to prevent accidental use, not malicious intent. All users will have to be granted permissions to all data still, so the auth system doesnt look like it will help. Example: user A will have access to data in database db1 as well as db2. When in the context of db1, we don't want them to use data from db2. When in the context of db2, they can indeed use data from db2. The goal is to contain all access when in the context of a database to just data in that database. Allow disabling foreign table access (cross database) using hiveconf Key: HIVE-3016 URL: https://issues.apache.org/jira/browse/HIVE-3016 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Sambavi Muthukrishnan Assignee: Sambavi Muthukrishnan Priority: Minor Attachments: hive-3016.1.patch.txt Original Estimate: 48h Remaining Estimate: 48h Disallow cross database access to tables using Y.T syntax under a specific configuration in HiveConf. i.e. when hive.error.on.crossdatabaseaccess is set to true, return an error when Y.T syntax is used to access tables and Y is not the current database. This can be set both via the client and in hive-site.xml, and will default to false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-1719) Move RegexSerDe out of hive-contrib and over to hive-serde
[ https://issues.apache.org/jira/browse/HIVE-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277052#comment-13277052 ] Phabricator commented on HIVE-1719: --- cwsteinbach has accepted the revision HIVE-1719 [jira] Move RegexSerDe out of hive-contrib and over to hive-serde. +1. Will commit if tests pass. REVISION DETAIL https://reviews.facebook.net/D3249 BRANCH HIVE-1719-trunk To: JIRA, cwsteinbach, shreepadma Move RegexSerDe out of hive-contrib and over to hive-serde -- Key: HIVE-1719 URL: https://issues.apache.org/jira/browse/HIVE-1719 Project: Hive Issue Type: Task Components: Serializers/Deserializers Reporter: Carl Steinbach Assignee: Shreepadma Venugopalan Attachments: HIVE-1719.3.patch.txt, HIVE-1719.D3051.1.patch, HIVE-1719.D3051.2.patch, HIVE-1719.D3141.1.patch, HIVE-1719.D3249.1.patch, HIVE-1719.D3249.1.patch, HIVE-1719.D3249.2.patch, HIVE-1719.D3249.3.patch, HIVE-1719.patch RegexSerDe is as much a part of the standard Hive distribution as the other SerDes currently in hive-serde. I think we should move it over to the hive-serde module so that users don't have to go to the added effort of manually registering the contrib jar before using it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3030) escape more chars for script operator
[ https://issues.apache.org/jira/browse/HIVE-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277054#comment-13277054 ] Namit Jain commented on HIVE-3030: -- @Carl, I will address the comments. I am not sure, why arc stopped working since yesterday. Let me play around with it. I agree, having comments on jira is necessary escape more chars for script operator - Key: HIVE-3030 URL: https://issues.apache.org/jira/browse/HIVE-3030 Project: Hive Issue Type: Bug Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Only new line was being escaped. The same behavior needs to be done for carriage returns, and tabs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3016) Allow disabling foreign table access (cross database) using hiveconf
[ https://issues.apache.org/jira/browse/HIVE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277087#comment-13277087 ] Carl Steinbach commented on HIVE-3016: -- bq. Example: user A will have access to data in database db1 as well as db2. When in the context of db1, we don't want them to use data from db2. When in the context of db2, they can indeed use data from db2. The goal is to contain all access when in the context of a database to just data in that database. I'm having a hard time understanding why you would want to enforce this restriction. What's the motivation for doing this? Allow disabling foreign table access (cross database) using hiveconf Key: HIVE-3016 URL: https://issues.apache.org/jira/browse/HIVE-3016 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Sambavi Muthukrishnan Assignee: Sambavi Muthukrishnan Priority: Minor Attachments: hive-3016.1.patch.txt Original Estimate: 48h Remaining Estimate: 48h Disallow cross database access to tables using Y.T syntax under a specific configuration in HiveConf. i.e. when hive.error.on.crossdatabaseaccess is set to true, return an error when Y.T syntax is used to access tables and Y is not the current database. This can be set both via the client and in hive-site.xml, and will default to false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3004) RegexSerDe should support other column types in addition to STRING
[ https://issues.apache.org/jira/browse/HIVE-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shreepadma Venugopalan updated HIVE-3004: - Attachment: #HIVE-3004.patch# RegexSerDe should support other column types in addition to STRING -- Key: HIVE-3004 URL: https://issues.apache.org/jira/browse/HIVE-3004 Project: Hive Issue Type: Improvement Components: Serializers/Deserializers Reporter: Carl Steinbach Assignee: Shreepadma Venugopalan Attachments: #HIVE-3004.patch# -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3004) RegexSerDe should support other column types in addition to STRING
[ https://issues.apache.org/jira/browse/HIVE-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shreepadma Venugopalan updated HIVE-3004: - Status: Patch Available (was: Open) RegexSerDe should support other column types in addition to STRING -- Key: HIVE-3004 URL: https://issues.apache.org/jira/browse/HIVE-3004 Project: Hive Issue Type: Improvement Components: Serializers/Deserializers Reporter: Carl Steinbach Assignee: Shreepadma Venugopalan Attachments: #HIVE-3004.patch# -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3004) RegexSerDe should support other column types in addition to STRING
[ https://issues.apache.org/jira/browse/HIVE-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shreepadma Venugopalan updated HIVE-3004: - Attachment: HIVE-3004-1.patch RegexSerDe should support other column types in addition to STRING -- Key: HIVE-3004 URL: https://issues.apache.org/jira/browse/HIVE-3004 Project: Hive Issue Type: Improvement Components: Serializers/Deserializers Reporter: Carl Steinbach Assignee: Shreepadma Venugopalan Attachments: HIVE-3004-1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3004) RegexSerDe should support other column types in addition to STRING
[ https://issues.apache.org/jira/browse/HIVE-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shreepadma Venugopalan updated HIVE-3004: - Attachment: (was: #HIVE-3004.patch#) RegexSerDe should support other column types in addition to STRING -- Key: HIVE-3004 URL: https://issues.apache.org/jira/browse/HIVE-3004 Project: Hive Issue Type: Improvement Components: Serializers/Deserializers Reporter: Carl Steinbach Assignee: Shreepadma Venugopalan Attachments: HIVE-3004-1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3030) escape more chars for script operator
[ https://issues.apache.org/jira/browse/HIVE-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain updated HIVE-3030: - Status: Patch Available (was: Open) escape more chars for script operator - Key: HIVE-3030 URL: https://issues.apache.org/jira/browse/HIVE-3030 Project: Hive Issue Type: Bug Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Only new line was being escaped. The same behavior needs to be done for carriage returns, and tabs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3030) escape more chars for script operator
[ https://issues.apache.org/jira/browse/HIVE-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277160#comment-13277160 ] Namit Jain commented on HIVE-3030: -- I addressed the comments. I could not make arc work with jira. Copying the old comments from Carl for reference: conf/hive-default.xml.template 1276 ↗ (On Diff #10293) I think this should be called 'hive.transform.escape.input' since the fact that this affects the behavior of the ScriptOperator is an implementation detail that is hidden from users. ql/src/java/org/apache/hadoop/hive/ql/metadata/HiveUtils.java 118 ↗ (On Diff #10293) Please remove these braces. ql/src/test/queries/clientpositive/newline.q 2 ↗ (On Diff #10293) Please add a test that transforms data containing TABs and carriage returns. escape more chars for script operator - Key: HIVE-3030 URL: https://issues.apache.org/jira/browse/HIVE-3030 Project: Hive Issue Type: Bug Components: Query Processor Reporter: Namit Jain Assignee: Namit Jain Only new line was being escaped. The same behavior needs to be done for carriage returns, and tabs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3029) Update ShimLoader to work with Hadoop 2.x
[ https://issues.apache.org/jira/browse/HIVE-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277194#comment-13277194 ] Phabricator commented on HIVE-3029: --- ashutoshc has accepted the revision HIVE-3029 [jira] Update ShimLoader to work with Hadoop 2.x. Feel free to commit after updating the comments. INLINE COMMENTS shims/src/common/java/org/apache/hadoop/hive/shims/ShimLoader.java:109-110 Comment look stale. Can you update it? REVISION DETAIL https://reviews.facebook.net/D3255 BRANCH HIVE-3029-shimloader To: JIRA, ashutoshc, cwsteinbach Update ShimLoader to work with Hadoop 2.x - Key: HIVE-3029 URL: https://issues.apache.org/jira/browse/HIVE-3029 Project: Hive Issue Type: Bug Components: Shims Reporter: Carl Steinbach Assignee: Carl Steinbach Attachments: HIVE-3029.D3255.1.patch, HIVE-3029.D3255.1.patch -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3016) Allow disabling foreign table access (cross database) using hiveconf
[ https://issues.apache.org/jira/browse/HIVE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277301#comment-13277301 ] Edward Capriolo commented on HIVE-3016: --- I am -1 on this. Authorization already covers this. Even if it did not, this is a arbitrary restriction for a specific use case. Growing the code base to support one-off type use cases does not benefit the community. Allow disabling foreign table access (cross database) using hiveconf Key: HIVE-3016 URL: https://issues.apache.org/jira/browse/HIVE-3016 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Sambavi Muthukrishnan Assignee: Sambavi Muthukrishnan Priority: Minor Attachments: hive-3016.1.patch.txt Original Estimate: 48h Remaining Estimate: 48h Disallow cross database access to tables using Y.T syntax under a specific configuration in HiveConf. i.e. when hive.error.on.crossdatabaseaccess is set to true, return an error when Y.T syntax is used to access tables and Y is not the current database. This can be set both via the client and in hive-site.xml, and will default to false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3016) Allow disabling foreign table access (cross database) using hiveconf
[ https://issues.apache.org/jira/browse/HIVE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277310#comment-13277310 ] Edward Capriolo commented on HIVE-3016: --- Maybe this could be a Hook that can be implemented by the end user. Allow disabling foreign table access (cross database) using hiveconf Key: HIVE-3016 URL: https://issues.apache.org/jira/browse/HIVE-3016 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Sambavi Muthukrishnan Assignee: Sambavi Muthukrishnan Priority: Minor Attachments: hive-3016.1.patch.txt Original Estimate: 48h Remaining Estimate: 48h Disallow cross database access to tables using Y.T syntax under a specific configuration in HiveConf. i.e. when hive.error.on.crossdatabaseaccess is set to true, return an error when Y.T syntax is used to access tables and Y is not the current database. This can be set both via the client and in hive-site.xml, and will default to false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3016) Allow disabling foreign table access (cross database) using hiveconf
[ https://issues.apache.org/jira/browse/HIVE-3016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277488#comment-13277488 ] Sambavi Muthukrishnan commented on HIVE-3016: - To enable better tracking of capacity utilization by teams sharing the warehouse, we want the ability to group users by teams and let them operate within a database as their logical container. The operation of using data in another database would require explicitly “linking” of the data into their database so we can track the storage capacity clearly. Auth wont do this for us, since a user could concurrently be operating against two databases that he/she is allowed to operate on. This would be useful in general for any shared warehouses. Edward: can you please elaborate on what you mean by this could be a hook? Allow disabling foreign table access (cross database) using hiveconf Key: HIVE-3016 URL: https://issues.apache.org/jira/browse/HIVE-3016 Project: Hive Issue Type: Improvement Components: Query Processor Reporter: Sambavi Muthukrishnan Assignee: Sambavi Muthukrishnan Priority: Minor Attachments: hive-3016.1.patch.txt Original Estimate: 48h Remaining Estimate: 48h Disallow cross database access to tables using Y.T syntax under a specific configuration in HiveConf. i.e. when hive.error.on.crossdatabaseaccess is set to true, return an error when Y.T syntax is used to access tables and Y is not the current database. This can be set both via the client and in hive-site.xml, and will default to false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
