[jira] [Assigned] (HIVE-25667) Unify code managing JDBC databases in tests
[ https://issues.apache.org/jira/browse/HIVE-25667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori reassigned HIVE-25667: --- Assignee: (was: Mark Bathori) > Unify code managing JDBC databases in tests > --- > > Key: HIVE-25667 > URL: https://issues.apache.org/jira/browse/HIVE-25667 > Project: Hive > Issue Type: Task > Components: Testing Infrastructure >Affects Versions: 4.0.0 >Reporter: Stamatis Zampetakis >Priority: Major > Labels: pull-request-available > Time Spent: 3h 10m > Remaining Estimate: 0h > > Currently there are two class hierarchies managing JDBC databases in tests, > [DatabaseRule|https://github.com/apache/hive/blob/d35de014dd49fdcfe0aacb68e6c587beff6d1dea/standalone-metastore/metastore-server/src/test/java/org/apache/hadoop/hive/metastore/dbinstall/rules/DatabaseRule.java] > and > [AbstractExternalDB|https://github.com/apache/hive/blob/d35de014dd49fdcfe0aacb68e6c587beff6d1dea/itests/util/src/main/java/org/apache/hadoop/hive/ql/externalDB/AbstractExternalDB.java]. > There are many similarities between these hierarchies and certain parts are > duplicated. > The goal of this JIRA is to refactor the aforementioned hierarchies to reduce > code duplication and improve extensibility. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (HIVE-23648) Fix FindBug issues in hive-serde
[ https://issues.apache.org/jira/browse/HIVE-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori reassigned HIVE-23648: --- Assignee: (was: Mark Bathori) > Fix FindBug issues in hive-serde > > > Key: HIVE-23648 > URL: https://issues.apache.org/jira/browse/HIVE-23648 > Project: Hive > Issue Type: Sub-task >Reporter: Panagiotis Garefalakis >Priority: Major > Labels: pull-request-available > Attachments: spotbugsXml.xml > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (HIVE-25266) Fix TestWarehouseExternalDir
[ https://issues.apache.org/jira/browse/HIVE-25266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori reassigned HIVE-25266: --- Assignee: (was: Mark Bathori) > Fix TestWarehouseExternalDir > > > Key: HIVE-25266 > URL: https://issues.apache.org/jira/browse/HIVE-25266 > Project: Hive > Issue Type: Bug >Reporter: Zoltan Haindrich >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > test is unstable > http://ci.hive.apache.org/job/hive-flaky-check/244/ -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (HIVE-25668) Support database reuse when using qt:database option
[
https://issues.apache.org/jira/browse/HIVE-25668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori reassigned HIVE-25668:
---
Assignee: (was: Mark Bathori)
> Support database reuse when using qt:database option
>
>
> Key: HIVE-25668
> URL: https://issues.apache.org/jira/browse/HIVE-25668
> Project: Hive
> Issue Type: Task
> Components: Testing Infrastructure
>Reporter: Stamatis Zampetakis
>Priority: Major
>
> With HIVE-25594 it is possible to initialize and use various types of
> databases in tests. At the moment all the supported databases rely on docker
> containers which are initialized/destroyed in per test basis. This is good in
> terms of test isolation but it brings a certain performance overhead slowing
> down tests. At the moment it is fine since the feature it is not widely used
> but it would be good to have a way to reuse a database in multiple qfiles.
> The developper could specify in the qfile if they want to reuse a container
> (if it is possible) by passing certain additional options. The declaration
> could look like below:
> {noformat}
> --!qt:database:type=mysql;script=q_test_country_table.sql;reuse=true{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (HIVE-25623) Create a parametrized test to check against the disabled MIN_HISTORY config
[ https://issues.apache.org/jira/browse/HIVE-25623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori reassigned HIVE-25623: --- Assignee: (was: Mark Bathori) > Create a parametrized test to check against the disabled MIN_HISTORY config > --- > > Key: HIVE-25623 > URL: https://issues.apache.org/jira/browse/HIVE-25623 > Project: Hive > Issue Type: Task >Reporter: Denys Kuzmenko >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Currently all test cases in TestDbTxnManager2/TestCommands(X) run against > enabled MIN_HISTORY config. We should also execute them for the scenario when > MIN_HISTORY_LEVEL table is missing. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (HIVE-23648) Fix FindBug issues in hive-serde
[ https://issues.apache.org/jira/browse/HIVE-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori updated HIVE-23648: Status: Patch Available (was: Open) > Fix FindBug issues in hive-serde > > > Key: HIVE-23648 > URL: https://issues.apache.org/jira/browse/HIVE-23648 > Project: Hive > Issue Type: Sub-task >Reporter: Panagiotis Garefalakis >Assignee: Mark Bathori >Priority: Major > Labels: pull-request-available > Attachments: spotbugsXml.xml > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (HIVE-23648) Fix FindBug issues in hive-serde
[ https://issues.apache.org/jira/browse/HIVE-23648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori reassigned HIVE-23648: --- Assignee: Mark Bathori > Fix FindBug issues in hive-serde > > > Key: HIVE-23648 > URL: https://issues.apache.org/jira/browse/HIVE-23648 > Project: Hive > Issue Type: Sub-task >Reporter: Panagiotis Garefalakis >Assignee: Mark Bathori >Priority: Major > Labels: pull-request-available > Attachments: spotbugsXml.xml > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HIVE-25266) Fix TestWarehouseExternalDir
[ https://issues.apache.org/jira/browse/HIVE-25266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori updated HIVE-25266: Status: Patch Available (was: Open) > Fix TestWarehouseExternalDir > > > Key: HIVE-25266 > URL: https://issues.apache.org/jira/browse/HIVE-25266 > Project: Hive > Issue Type: Bug >Reporter: Zoltan Haindrich >Assignee: Mark Bathori >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > test is unstable > http://ci.hive.apache.org/job/hive-flaky-check/244/ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (HIVE-25266) Fix TestWarehouseExternalDir
[ https://issues.apache.org/jira/browse/HIVE-25266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori reassigned HIVE-25266: --- Assignee: Mark Bathori > Fix TestWarehouseExternalDir > > > Key: HIVE-25266 > URL: https://issues.apache.org/jira/browse/HIVE-25266 > Project: Hive > Issue Type: Bug >Reporter: Zoltan Haindrich >Assignee: Mark Bathori >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > test is unstable > http://ci.hive.apache.org/job/hive-flaky-check/244/ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (HIVE-25668) Support database reuse when using qt:database option
[
https://issues.apache.org/jira/browse/HIVE-25668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori reassigned HIVE-25668:
---
Assignee: Mark Bathori
> Support database reuse when using qt:database option
>
>
> Key: HIVE-25668
> URL: https://issues.apache.org/jira/browse/HIVE-25668
> Project: Hive
> Issue Type: Task
> Components: Testing Infrastructure
>Reporter: Stamatis Zampetakis
>Assignee: Mark Bathori
>Priority: Major
>
> With HIVE-25594 it is possible to initialize and use various types of
> databases in tests. At the moment all the supported databases rely on docker
> containers which are initialized/destroyed in per test basis. This is good in
> terms of test isolation but it brings a certain performance overhead slowing
> down tests. At the moment it is fine since the feature it is not widely used
> but it would be good to have a way to reuse a database in multiple qfiles.
> The developper could specify in the qfile if they want to reuse a container
> (if it is possible) by passing certain additional options. The declaration
> could look like below:
> {noformat}
> --!qt:database:type=mysql;script=q_test_country_table.sql;reuse=true{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HIVE-25667) Unify code managing JDBC databases in tests
[ https://issues.apache.org/jira/browse/HIVE-25667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori updated HIVE-25667: Status: Patch Available (was: Open) > Unify code managing JDBC databases in tests > --- > > Key: HIVE-25667 > URL: https://issues.apache.org/jira/browse/HIVE-25667 > Project: Hive > Issue Type: Task > Components: Testing Infrastructure >Affects Versions: 4.0.0 >Reporter: Stamatis Zampetakis >Assignee: Mark Bathori >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Currently there are two class hierarchies managing JDBC databases in tests, > [DatabaseRule|https://github.com/apache/hive/blob/d35de014dd49fdcfe0aacb68e6c587beff6d1dea/standalone-metastore/metastore-server/src/test/java/org/apache/hadoop/hive/metastore/dbinstall/rules/DatabaseRule.java] > and > [AbstractExternalDB|https://github.com/apache/hive/blob/d35de014dd49fdcfe0aacb68e6c587beff6d1dea/itests/util/src/main/java/org/apache/hadoop/hive/ql/externalDB/AbstractExternalDB.java]. > There are many similarities between these hierarchies and certain parts are > duplicated. > The goal of this JIRA is to refactor the aforementioned hierarchies to reduce > code duplication and improve extensibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (HIVE-25623) Create a parametrized test to check against the disabled MIN_HISTORY config
[ https://issues.apache.org/jira/browse/HIVE-25623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori updated HIVE-25623: Status: Patch Available (was: Open) > Create a parametrized test to check against the disabled MIN_HISTORY config > --- > > Key: HIVE-25623 > URL: https://issues.apache.org/jira/browse/HIVE-25623 > Project: Hive > Issue Type: Task >Reporter: Denys Kuzmenko >Assignee: Mark Bathori >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Currently all test cases in TestDbTxnManager2/TestCommands(X) run against > enabled MIN_HISTORY config. We should also execute them for the scenario when > MIN_HISTORY_LEVEL table is missing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (HIVE-25667) Unify code managing JDBC databases in tests
[ https://issues.apache.org/jira/browse/HIVE-25667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori reassigned HIVE-25667: --- Assignee: Mark Bathori > Unify code managing JDBC databases in tests > --- > > Key: HIVE-25667 > URL: https://issues.apache.org/jira/browse/HIVE-25667 > Project: Hive > Issue Type: Task > Components: Testing Infrastructure >Affects Versions: 4.0.0 >Reporter: Stamatis Zampetakis >Assignee: Mark Bathori >Priority: Major > > Currently there are two class hierarchies managing JDBC databases in tests, > [DatabaseRule|https://github.com/apache/hive/blob/d35de014dd49fdcfe0aacb68e6c587beff6d1dea/standalone-metastore/metastore-server/src/test/java/org/apache/hadoop/hive/metastore/dbinstall/rules/DatabaseRule.java] > and > [AbstractExternalDB|https://github.com/apache/hive/blob/d35de014dd49fdcfe0aacb68e6c587beff6d1dea/itests/util/src/main/java/org/apache/hadoop/hive/ql/externalDB/AbstractExternalDB.java]. > There are many similarities between these hierarchies and certain parts are > duplicated. > The goal of this JIRA is to refactor the aforementioned hierarchies to reduce > code duplication and improve extensibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (HIVE-25623) Create a parametrized test to check against the disabled MIN_HISTORY config
[ https://issues.apache.org/jira/browse/HIVE-25623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Bathori reassigned HIVE-25623: --- Assignee: Mark Bathori > Create a parametrized test to check against the disabled MIN_HISTORY config > --- > > Key: HIVE-25623 > URL: https://issues.apache.org/jira/browse/HIVE-25623 > Project: Hive > Issue Type: Task >Reporter: Denys Kuzmenko >Assignee: Mark Bathori >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Currently all test cases in TestDbTxnManager2/TestCommands(X) run against > enabled MIN_HISTORY config. We should also execute them for the scenario when > MIN_HISTORY_LEVEL table is missing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (HIVE-25686) UDFSpace result length calculation is incorrect after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443887#comment-17443887
]
Mark Bathori edited comment on HIVE-25686 at 11/15/21, 3:38 PM:
[~zabetak] yes, the problem does not occur in the current version. Currently
both the old and the new method call returns with the same correct value.
was (Author: mbathori):
[~zabetak] yes, the problem does not occur in the current version. Both the old
and the new method call returns with the same value currently.
> UDFSpace result length calculation is incorrect after HADOOP-17901 and
> HADOOP-17905
> ---
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Assignee: Mark Bathori
>Priority: Critical
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the result length is
> not determined correctly. It is causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using {color:#ff}--outputformat=csv{color} the generated file
> contains 0 ascii characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (HIVE-25686) UDFSpace result length calculation is incorrect after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443887#comment-17443887
]
Mark Bathori commented on HIVE-25686:
-
[~zabetak] yes, the problem does not occur in the current version. Both the old
and the new method call returns with the same value currently.
> UDFSpace result length calculation is incorrect after HADOOP-17901 and
> HADOOP-17905
> ---
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Assignee: Mark Bathori
>Priority: Critical
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the result length is
> not determined correctly. It is causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using {color:#ff}--outputformat=csv{color} the generated file
> contains 0 ascii characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HIVE-25686) UDFSpace result length calculation is incorrect after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori updated HIVE-25686:
Status: Patch Available (was: Open)
> UDFSpace result length calculation is incorrect after HADOOP-17901 and
> HADOOP-17905
> ---
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Assignee: Mark Bathori
>Priority: Critical
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the result length is
> not determined correctly. It is causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using {color:#ff}--outputformat=csv{color} the generated file
> contains 0 ascii characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HIVE-25686) UDFSpace result length calculation is incorrect after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori updated HIVE-25686:
Description:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the result length is not
determined correctly. It is causing unexpected characters in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using {color:#ff}--outputformat=csv{color} the generated file
contains 0 ascii characters(“EOF”) instead of spaces.
was:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It is causing unexpected characters in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using {color:#ff}--outputformat=csv{color} the generated file
contains 0 ascii characters(“EOF”) instead of spaces.
> UDFSpace result length calculation is incorrect after HADOOP-17901 and
> HADOOP-17905
> ---
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Assignee: Mark Bathori
>Priority: Critical
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the result length is
> not determined correctly. It is causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using {color:#ff}--outputformat=csv{color} the generated file
> contains 0 ascii characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HIVE-25686) UDFSpace result length calculation is incorrect after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori updated HIVE-25686:
Summary: UDFSpace result length calculation is incorrect after HADOOP-17901
and HADOOP-17905 (was: UDFSpace functionality issue after HADOOP-17901 and
HADOOP-17905)
> UDFSpace result length calculation is incorrect after HADOOP-17901 and
> HADOOP-17905
> ---
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Assignee: Mark Bathori
>Priority: Critical
> Fix For: 4.0.0
>
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the text length is not
> determined correctly. It is causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using {color:#ff}--outputformat=csv{color} the generated file
> contains 0 ascii characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HIVE-25686) UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori updated HIVE-25686:
Description:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It is causing unexpected characters in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using {color:#ff}--outputformat=csv{color} the generated file
contains 0 ascii characters(“EOF”) instead of spaces.
was:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It causing unexpected characters in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using {color:#FF}--outputformat=csv{color} the generated file
contains 0 ascii characters(“EOF”) instead of spaces.
> UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
>
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Assignee: Mark Bathori
>Priority: Critical
> Fix For: 4.0.0
>
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the text length is not
> determined correctly. It is causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using {color:#ff}--outputformat=csv{color} the generated file
> contains 0 ascii characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (HIVE-25686) UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori reassigned HIVE-25686:
---
Assignee: Mark Bathori
> UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
>
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Assignee: Mark Bathori
>Priority: Critical
> Fix For: 4.0.0
>
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the text length is not
> determined correctly. It causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using {color:#FF}--outputformat=csv{color} the generated file
> contains 0 ascii characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HIVE-25686) UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori updated HIVE-25686:
Description:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It causing unexpected characters in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using --outputformat=csv the generated file contains 0 ascii
characters(“EOF”) instead of spaces.
was:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It causing unexpected character in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using --outputformat=csv the generated file contains 0 ascii
characters(“EOF”) instead of spaces.
> UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
>
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Priority: Critical
> Fix For: 4.0.0
>
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the text length is not
> determined correctly. It causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using --outputformat=csv the generated file contains 0 ascii
> characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HIVE-25686) UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori updated HIVE-25686:
Description:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It causing unexpected characters in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using {color:#FF}--outputformat=csv{color} the generated file
contains 0 ascii characters(“EOF”) instead of spaces.
was:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It causing unexpected characters in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using --outputformat=csv the generated file contains 0 ascii
characters(“EOF”) instead of spaces.
> UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
>
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Priority: Critical
> Fix For: 4.0.0
>
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the text length is not
> determined correctly. It causing unexpected characters in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using {color:#FF}--outputformat=csv{color} the generated file
> contains 0 ascii characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (HIVE-25686) UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
[
https://issues.apache.org/jira/browse/HIVE-25686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bathori updated HIVE-25686:
Description:
The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It causing unexpected character in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using --outputformat=csv the generated file contains 0 ascii
characters(“EOF”) instead of spaces.
was:
The changes added in HADOOP-17901 and HADOOP-17905 ** introduced some issues in
Hive side. UDFSpace is generating false output because the text length is not
determined correctly. It causing unexpected character in the result.
*Repro steps:*
{code:java}
create table t(i int);{code}
{code:java}
insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
{code:java}
select i, SPACE(i) from t;{code}
Faulty output:
{code:java}
+-+-+
| i | _c1 |
+-+-+
| 5 | |
| 6 | |
| 7 | |
| 8 | |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
+-+-+
{code}
Also by using --outputformat=csv the generated file contains 0 ascii
characters(“EOF”) instead of spaces.
> UDFSpace functionality issue after HADOOP-17901 and HADOOP-17905
>
>
> Key: HIVE-25686
> URL: https://issues.apache.org/jira/browse/HIVE-25686
> Project: Hive
> Issue Type: Bug
> Components: Hive
>Reporter: Mark Bathori
>Priority: Critical
> Fix For: 4.0.0
>
>
> The changes added in HADOOP-17901 and HADOOP-17905 introduced some issues in
> Hive side. UDFSpace is generating false output because the text length is not
> determined correctly. It causing unexpected character in the result.
> *Repro steps:*
> {code:java}
> create table t(i int);{code}
> {code:java}
> insert into t values (5),(6),(7),(8),(9),(10),(11),(12),(13),(14);{code}
> {code:java}
> select i, SPACE(i) from t;{code}
>
> Faulty output:
> {code:java}
> +-+-+
> | i | _c1 |
> +-+-+
> | 5 | |
> | 6 | |
> | 7 | |
> | 8 | |
> | 9 | |
> | 10 | |
> | 11 | |
> | 12 | |
> | 13 | |
> | 14 | |
> +-+-+
> {code}
>
> Also by using --outputformat=csv the generated file contains 0 ascii
> characters(“EOF”) instead of spaces.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
