[jira] [Commented] (HIVE-19256) UDF which shapes the input data according to the specified schema
[
https://issues.apache.org/jira/browse/HIVE-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16527304#comment-16527304
]
Hive QA commented on HIVE-19256:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12920050/HIVE-19256_1.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 14636 tests
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[show_functions]
(batchId=76)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/12238/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12238/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12238/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12920050 - PreCommit-HIVE-Build
> UDF which shapes the input data according to the specified schema
> -
>
> Key: HIVE-19256
> URL: https://issues.apache.org/jira/browse/HIVE-19256
> Project: Hive
> Issue Type: New Feature
> Components: Hive
>Affects Versions: 3.1.0
>Reporter: Ratandeep Ratti
>Assignee: Ratandeep Ratti
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: HIVE-19256.patch, HIVE-19256_1.patch
>
>
> We use this UDF a lot in our org. This UDF takes an object and a Hive schema
> and make sure the output object matches the schema completely. In some
> respects it is similar to {{named
> _struct}} UDF which can be used to select columns from a struct, but it is
> more general since it can work not only on structs, but all Hive data types
> (expect union). Also the schema can provide certain valid type conversions
> (int -> double etc)
> One scenario where this is quite useful is making sure that the Hive view
> created with a specific schema will have columns which will always match that
> schema. In Hive today when a view is created, new nested columns from the
> underlying table can leak out from the view, even though the user never
> wanted this behavior. Note that this leaking of columns is only for nested
> columns and not for top level columns, so in that regard this behavior of
> Hive is inconsistent.
> Sample usage of the UDF
> {code}
> generic_project(col, "struct>>") // Returning
> data which matches the input schema. Here extra columns which are not part of
> the input will be removed
> generic_project(col, "struct") // If the input column had a struct
> with col a as int . It would type cast 'a' to double.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HIVE-19256) UDF which shapes the input data according to the specified schema
[
https://issues.apache.org/jira/browse/HIVE-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16527296#comment-16527296
]
Hive QA commented on HIVE-19256:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
48s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
0s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m
59s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m
11s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 5m
58s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
12s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 40m 34s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense javac javadoc findbugs checkstyle compile |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-12238/dev-support/hive-personality.sh
|
| git revision | master / 5b2cbb5 |
| Default Java | 1.8.0_111 |
| modules | C: . U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-12238/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> UDF which shapes the input data according to the specified schema
> -
>
> Key: HIVE-19256
> URL: https://issues.apache.org/jira/browse/HIVE-19256
> Project: Hive
> Issue Type: New Feature
> Components: Hive
>Affects Versions: 3.1.0
>Reporter: Ratandeep Ratti
>Assignee: Ratandeep Ratti
>Priority: Major
> Fix For: 3.2.0
>
> Attachments: HIVE-19256.patch, HIVE-19256_1.patch
>
>
> We use this UDF a lot in our org. This UDF takes an object and a Hive schema
> and make sure the output object matches the schema completely. In some
> respects it is similar to {{named
> _struct}} UDF which can be used to select columns from a struct, but it is
> more general since it can work not only on structs, but all Hive data types
> (expect union). Also the schema can provide certain valid type conversions
> (int -> double etc)
> One scenario where this is quite useful is making sure that the Hive view
> created with a specific schema will have columns which will always match that
> schema. In Hive today when a view is created, new nested columns from the
> underlying table can leak out from the view, even though the user never
> wanted this behavior. Note that this leaking of columns is only for nested
> columns and not for top level columns, so in that regard this behavior of
> Hive is inconsistent.
> Sample usage of the UDF
> {code}
> generic_project(col, "struct>>") // Returning
> data which matches the input schema. Here extra columns which are not part of
> the input will be removed
> generic_project(col, "struct") // If the input column had a struct
> with col a
[jira] [Commented] (HIVE-19256) UDF which shapes the input data according to the specified schema
[
https://issues.apache.org/jira/browse/HIVE-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446857#comment-16446857
]
Hive QA commented on HIVE-19256:
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12920050/HIVE-19256_1.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:red}ERROR:{color} -1 due to 22 failed/errored test(s), 14286 tests
executed
*Failed tests:*
{noformat}
TestMinimrCliDriver - did not produce a TEST-*.xml file (likely timed out)
(batchId=93)
[infer_bucket_sort_num_buckets.q,infer_bucket_sort_reducers_power_two.q,parallel_orderby.q,bucket_num_reducers_acid.q,infer_bucket_sort_map_operators.q,infer_bucket_sort_merge.q,root_dir_external_table.q,infer_bucket_sort_dyn_part.q,udf_using.q,bucket_num_reducers_acid2.q]
TestNonCatCallsWithCatalog - did not produce a TEST-*.xml file (likely timed
out) (batchId=217)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[parquet_vectorization_0]
(batchId=17)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[results_cache_invalidation2]
(batchId=39)
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver[show_functions]
(batchId=75)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[bucket_map_join_tez1]
(batchId=175)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[default_constraint]
(batchId=163)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[results_cache_invalidation2]
(batchId=163)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[sysdb]
(batchId=163)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[tez_smb_1]
(batchId=171)
org.apache.hadoop.hive.cli.TestMiniSparkOnYarnCliDriver.testCliDriver[bucketizedhiveinputformat]
(batchId=183)
org.apache.hadoop.hive.cli.TestMiniTezCliDriver.testCliDriver[explainanalyze_5]
(batchId=105)
org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[cluster_tasklog_retrieval]
(batchId=98)
org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[mapreduce_stack_trace]
(batchId=98)
org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[mapreduce_stack_trace_turnoff]
(batchId=98)
org.apache.hadoop.hive.cli.TestNegativeMinimrCliDriver.testCliDriver[minimr_broken_pipe]
(batchId=98)
org.apache.hadoop.hive.ql.TestAcidOnTez.testAcidInsertWithRemoveUnion
(batchId=228)
org.apache.hadoop.hive.ql.TestAcidOnTez.testCtasTezUnion (batchId=228)
org.apache.hadoop.hive.ql.TestAcidOnTez.testNonStandardConversion01
(batchId=228)
org.apache.hadoop.hive.ql.TestMTQueries.testMTQueries1 (batchId=232)
org.apache.hive.beeline.TestBeeLineWithArgs.testQueryProgress (batchId=235)
org.apache.hive.minikdc.TestJdbcWithMiniKdcCookie.testCookieNegative
(batchId=254)
{noformat}
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/10389/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/10389/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-10389/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 22 tests failed
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12920050 - PreCommit-HIVE-Build
> UDF which shapes the input data according to the specified schema
> -
>
> Key: HIVE-19256
> URL: https://issues.apache.org/jira/browse/HIVE-19256
> Project: Hive
> Issue Type: New Feature
> Components: Hive
>Affects Versions: 3.1.0
>Reporter: Ratandeep Ratti
>Assignee: Ratandeep Ratti
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: HIVE-19256.patch, HIVE-19256_1.patch
>
>
> We use this UDF a lot in our org. This UDF takes an object and a Hive schema
> and make sure the output object matches the schema completely. In some
> respects it is similar to {{named
> _struct}} UDF which can be used to select columns from a struct, but it is
> more general since it can work not only on structs, but all Hive data types
> (expect union). Also the schema can provide certain valid type conversions
> (int -> double etc)
> One scenario where this is quite useful is making sure that the Hive view
> created with a specific schema will have columns which will always match that
> schema. In Hive today when a view is created, new nested columns from the
> underlying table can leak out from the view, even though the user never
> wanted this behavior. Note that this leaking of columns is only for
[jira] [Commented] (HIVE-19256) UDF which shapes the input data according to the specified schema
[
https://issues.apache.org/jira/browse/HIVE-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446845#comment-16446845
]
Hive QA commented on HIVE-19256:
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 8m
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
16s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 6m
27s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 6m
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 6m
58s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 44m 3s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Optional Tests | asflicense javac javadoc findbugs checkstyle compile |
| uname | Linux hiveptest-server-upstream 3.16.0-4-amd64 #1 SMP Debian
3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/data/hiveptest/working/yetus_PreCommit-HIVE-Build-10389/dev-support/hive-personality.sh
|
| git revision | master / 97503fb |
| Default Java | 1.8.0_111 |
| modules | C: . U: . |
| Console output |
http://104.198.109.242/logs//PreCommit-HIVE-Build-10389/yetus.txt |
| Powered by | Apache Yetushttp://yetus.apache.org |
This message was automatically generated.
> UDF which shapes the input data according to the specified schema
> -
>
> Key: HIVE-19256
> URL: https://issues.apache.org/jira/browse/HIVE-19256
> Project: Hive
> Issue Type: New Feature
> Components: Hive
>Affects Versions: 3.1.0
>Reporter: Ratandeep Ratti
>Assignee: Ratandeep Ratti
>Priority: Major
> Fix For: 3.1.0
>
> Attachments: HIVE-19256.patch, HIVE-19256_1.patch
>
>
> We use this UDF a lot in our org. This UDF takes an object and a Hive schema
> and make sure the output object matches the schema completely. In some
> respects it is similar to {{named
> _struct}} UDF which can be used to select columns from a struct, but it is
> more general since it can work not only on structs, but all Hive data types
> (expect union). Also the schema can provide certain valid type conversions
> (int -> double etc)
> One scenario where this is quite useful is making sure that the Hive view
> created with a specific schema will have columns which will always match that
> schema. In Hive today when a view is created, new nested columns from the
> underlying table can leak out from the view, even though the user never
> wanted this behavior. Note that this leaking of columns is only for nested
> columns and not for top level columns, so in that regard this behavior of
> Hive is inconsistent.
> Sample usage of the UDF
> {code}
> generic_project(col, "struct>>") // Returning
> data which matches the input schema. Here extra columns which are not part of
> the input will be removed
> generic_project(col, "struct") // If the input column had a struct
> with col a as int . It would type cast 'a' to double.
> {code}
--
This message was sent
[jira] [Commented] (HIVE-19256) UDF which shapes the input data according to the specified schema
[
https://issues.apache.org/jira/browse/HIVE-19256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16446064#comment-16446064
]
Ratandeep Ratti commented on HIVE-19256:
https://reviews.apache.org/r/66732
> UDF which shapes the input data according to the specified schema
> -
>
> Key: HIVE-19256
> URL: https://issues.apache.org/jira/browse/HIVE-19256
> Project: Hive
> Issue Type: New Feature
>Reporter: Ratandeep Ratti
>Assignee: Ratandeep Ratti
>Priority: Major
> Attachments: HIVE-19256.patch, HIVE-19256_1.patch
>
>
> We use this UDF a lot in our org. This UDF takes an object and a Hive schema
> and make sure the output object matches the schema completely. In some
> respects it is similar to {{named
> _struct}} UDF which can be used to select columns from a struct, but it is
> more general since it can work not only on structs, but all Hive data types
> (expect union). Also the schema can provide certain valid type conversions
> (int -> double etc)
> One scenario where this is quite useful is making sure that the Hive view
> created with a specific schema will have columns which will always match that
> schema. In Hive today when a view is created, new nested columns from the
> underlying table can leak out from the view, even though the user never
> wanted this behavior. Note that this leaking of columns is only for nested
> columns and not for top level columns, so in that regard this behavior of
> Hive is inconsistent.
> Sample usage of the UDF
> {code}
> generic_project(col, "struct>>") // Returning
> data which matches the input schema. Here extra columns which are not part of
> the input will be removed
> generic_project(col, "struct") // If the input column had a struct
> with col a as int . It would type cast 'a' to double.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
