[
https://issues.apache.org/jira/browse/HIVE-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brock Noland updated HIVE-4019:
-------------------------------
Attachment: HIVE-4019-1.patch
Hi guys,
I've rebased the original patch, attached. However, I am seeing a problem
during compilation because
output column names is null on TableFunctionResolver. It seems this on purpose
(See WIndowTableFunction) but I don't see any location to obtain the column
names.
RawInputColumnNames is also null. Any hints?
I have time to work on this tomorrow, but I don't want to hold up anything that
is important for
release so if this is holding anything up, please feel free to take it up.
{noformat}
2013-04-16 13:52:58,383 ERROR ql.Driver (SessionState.java:printError(401)) -
FAILED: NullPointerException null
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.parse.PTFTranslator.buildRowResolverForPTF(PTFTranslator.java:1016)
at
org.apache.hadoop.hive.ql.parse.PTFTranslator.translate(PTFTranslator.java:383)
at
org.apache.hadoop.hive.ql.parse.PTFTranslator.translatePTFChain(PTFTranslator.java:297)
at
org.apache.hadoop.hive.ql.parse.PTFTranslator.translate(PTFTranslator.java:134)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.translatePTFInvocationSpec(SemanticAnalyzer.java:10491)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPTFPlanForComponentQuery(SemanticAnalyzer.java:10623)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPTFPlan(SemanticAnalyzer.java:10498)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.genPlan(SemanticAnalyzer.java:7974)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:8701)
at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:279)
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.processLine(CliDriver.java:348)
at org.apache.hadoop.hive.ql.QTestUtil.executeClient(QTestUtil.java:790)
at
org.apache.hadoop.hive.cli.TestCliDriver.runTest(TestCliDriver.java:124)
at
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_ptf_register_tblfn(TestCliDriver.java:108)
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 junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:520)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1060)
at
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:911)
{noformat}
> Ability to create and drop temporary partition function
> -------------------------------------------------------
>
> Key: HIVE-4019
> URL: https://issues.apache.org/jira/browse/HIVE-4019
> Project: Hive
> Issue Type: New Feature
> Components: PTF-Windowing
> Reporter: Ashutosh Chauhan
> Assignee: Ashutosh Chauhan
> Attachments: HIVE-4019-1.patch, hive-4019.q
>
>
> Just like udf/udaf/udtf functions, user should be able to add and drop custom
> partitioning functions.
--
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
