[jira] [Resolved] (DRILL-7179) Compiling drill from source doesn't include all the jars in the distribution/target dir

2019-04-16 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li resolved DRILL-7179.
-
   Resolution: Fixed
Fix Version/s: 1.15.0

Compilation environment setting problem has been resolved.

> Compiling drill from source doesn't include all the jars in the 
> distribution/target dir
> ---
>
> Key: DRILL-7179
> URL: https://issues.apache.org/jira/browse/DRILL-7179
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Building on Windows 10
>Reporter: Georgi Perpeliev
>Assignee: Hefei Li
>Priority: Minor
> Fix For: 1.15.0
>
> Attachments: checkou.png, cmpiled.png, verify_tarball_file.png
>
>
> Following the instructions on 
> [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with 
> incomplete tarball including only drill-shaded-guava-23.0.jar in the jars 
> subdirectory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Comment Edited] (DRILL-7179) Compiling drill from source doesn't include all the jars in the distribution/target dir

2019-04-15 Thread Hefei Li (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818612#comment-16818612
 ] 

Hefei Li edited comment on DRILL-7179 at 4/16/19 4:14 AM:
--

@[~gperp]  My compiled steps as below, you can refer to it:

1. Clone the drill repository, and checkout the current statable version
{code:java}
git clone https://gitbox.apache.org/repos/asf/drill.git
git checkout -b branch_1.15.0 originon/1.15.0
{code}
  Then you can verify it as below:
{code:java}
git branch -vv
{code}
2. Compile the code
{code:java}
mvn clean package -e -DskipTests
{code}
  Please make sure your compilation process is successful. If not, please 
upload the error log.

3. Verify compilation results

  You can verify it with the following command:
{code:java}
tar -tf distribution/target/apache-drill-1.15.0.tar.gz | grep drill-shaded
{code}


was (Author: lhfei):
@[~gperp]  My compiled steps as below, you can refer to it:

1. Clone the drill repository, and checkout the current statable version

 
{code:java}
git clone https://gitbox.apache.org/repos/asf/drill.git
git checkout -b branch_1.15.0 originon/1.15.0
{code}
  Then you can verify it as below:

 
{code:java}
git branch -vv
{code}
 

 

 

2. Compile the code
{code:java}
mvn clean package -e -DskipTests
{code}
  Please make sure your compilation process is successful. If not, please 
upload the error log.

 

3. Verify compilation results

  You can verify it with the following command:

 
{code:java}
tar -tf distribution/target/apache-drill-1.15.0.tar.gz | grep drill-shaded
{code}
 

 

 

> Compiling drill from source doesn't include all the jars in the 
> distribution/target dir
> ---
>
> Key: DRILL-7179
> URL: https://issues.apache.org/jira/browse/DRILL-7179
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Building on Windows 10
>Reporter: Georgi Genchev Perpeliev
>Assignee: Hefei Li
>Priority: Minor
> Attachments: checkou.png, cmpiled.png, verify_tarball_file.png
>
>
> Following the instructions on 
> [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with 
> incomplete tarball including only drill-shaded-guava-23.0.jar in the jars 
> subdirectory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DRILL-7179) Compiling drill from source doesn't include all the jars in the distribution/target dir

2019-04-15 Thread Hefei Li (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818612#comment-16818612
 ] 

Hefei Li commented on DRILL-7179:
-

@[~gperp]  My compiled steps as below, you can refer to it:

1. Clone the drill repository, and checkout the current statable version

 
{code:java}
git clone https://gitbox.apache.org/repos/asf/drill.git
git checkout -b branch_1.15.0 originon/1.15.0
{code}
  Then you can verify it as below:

 
{code:java}
git branch -vv
{code}
 

 

 

2. Compile the code
{code:java}
mvn clean package -e -DskipTests
{code}
  Please make sure your compilation process is successful. If not, please 
upload the error log.

 

3. Verify compilation results

  You can verify it with the following command:

 
{code:java}
tar -tf distribution/target/apache-drill-1.15.0.tar.gz | grep drill-shaded
{code}
 

 

 

> Compiling drill from source doesn't include all the jars in the 
> distribution/target dir
> ---
>
> Key: DRILL-7179
> URL: https://issues.apache.org/jira/browse/DRILL-7179
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Building on Windows 10
>Reporter: Georgi Genchev Perpeliev
>Assignee: Hefei Li
>Priority: Minor
> Attachments: checkou.png, cmpiled.png, verify_tarball_file.png
>
>
> Following the instructions on 
> [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with 
> incomplete tarball including only drill-shaded-guava-23.0.jar in the jars 
> subdirectory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DRILL-7179) Compiling drill from source doesn't include all the jars in the distribution/target dir

2019-04-15 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li updated DRILL-7179:

Attachment: verify_tarball_file.png

> Compiling drill from source doesn't include all the jars in the 
> distribution/target dir
> ---
>
> Key: DRILL-7179
> URL: https://issues.apache.org/jira/browse/DRILL-7179
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Building on Windows 10
>Reporter: Georgi Genchev Perpeliev
>Assignee: Hefei Li
>Priority: Minor
> Attachments: checkou.png, cmpiled.png, verify_tarball_file.png
>
>
> Following the instructions on 
> [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with 
> incomplete tarball including only drill-shaded-guava-23.0.jar in the jars 
> subdirectory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DRILL-7179) Compiling drill from source doesn't include all the jars in the distribution/target dir

2019-04-15 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li updated DRILL-7179:

Attachment: cmpiled.png

> Compiling drill from source doesn't include all the jars in the 
> distribution/target dir
> ---
>
> Key: DRILL-7179
> URL: https://issues.apache.org/jira/browse/DRILL-7179
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Building on Windows 10
>Reporter: Georgi Genchev Perpeliev
>Assignee: Hefei Li
>Priority: Minor
> Attachments: checkou.png, cmpiled.png
>
>
> Following the instructions on 
> [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with 
> incomplete tarball including only drill-shaded-guava-23.0.jar in the jars 
> subdirectory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (DRILL-7179) Compiling drill from source doesn't include all the jars in the distribution/target dir

2019-04-15 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li updated DRILL-7179:

Attachment: checkou.png

> Compiling drill from source doesn't include all the jars in the 
> distribution/target dir
> ---
>
> Key: DRILL-7179
> URL: https://issues.apache.org/jira/browse/DRILL-7179
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Building on Windows 10
>Reporter: Georgi Genchev Perpeliev
>Assignee: Hefei Li
>Priority: Minor
> Attachments: checkou.png
>
>
> Following the instructions on 
> [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with 
> incomplete tarball including only drill-shaded-guava-23.0.jar in the jars 
> subdirectory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DRILL-7181) [Text V3 Reader] Exception with inadequate message is thrown if select columns as array with extractHeader set to true

2019-04-15 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li reassigned DRILL-7181:
---

Assignee: Hefei Li

> [Text V3 Reader] Exception with inadequate message is thrown if select 
> columns as array with extractHeader set to true
> --
>
> Key: DRILL-7181
> URL: https://issues.apache.org/jira/browse/DRILL-7181
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Anton Gozhiy
>Assignee: Hefei Li
>Priority: Major
>
> *Prerequisites:*
>  # Create a simple .csv file with header, like this:
> {noformat}
> col1,col2,col3
> 1,2,3
> 4,5,6
> 7,8,9
> {noformat}
>  # Set exec.storage.enable_v3_text_reader=true
>  # Set "extractHeader": true for csv format in dfs storage plugin.
> *Query:*
> {code:sql}
> select columns[0] from dfs.tmp.`/test.csv`
> {code}
> *Expected result:* Exception should happen, here is the message from V2 
> reader:
> {noformat}
> UNSUPPORTED_OPERATION ERROR: Drill Remote Exception
>   (java.lang.Exception) UNSUPPORTED_OPERATION ERROR: With extractHeader 
> enabled, only header names are supported
> column name columns
> column index
> Fragment 0:0
> [Error Id: 5affa696-1dbd-43d7-ac14-72d235c00f43 on userf87d-pc:31010]
> org.apache.drill.common.exceptions.UserException$Builder.build():630
> 
> org.apache.drill.exec.store.easy.text.compliant.FieldVarCharOutput.():106
> 
> org.apache.drill.exec.store.easy.text.compliant.CompliantTextRecordReader.setup():139
> org.apache.drill.exec.physical.impl.ScanBatch.getNextReaderIfHas():321
> org.apache.drill.exec.physical.impl.ScanBatch.internalNext():216
> org.apache.drill.exec.physical.impl.ScanBatch.next():271
> org.apache.drill.exec.record.AbstractRecordBatch.next():126
> org.apache.drill.exec.record.AbstractRecordBatch.next():116
> org.apache.drill.exec.record.AbstractUnaryRecordBatch.innerNext():63
> org.apache.drill.exec.physical.impl.limit.LimitRecordBatch.innerNext():101
> org.apache.drill.exec.record.AbstractRecordBatch.next():186
> org.apache.drill.exec.record.AbstractRecordBatch.next():126
> org.apache.drill.exec.record.AbstractRecordBatch.next():116
> org.apache.drill.exec.record.AbstractUnaryRecordBatch.innerNext():63
> org.apache.drill.exec.physical.impl.limit.LimitRecordBatch.innerNext():101
> org.apache.drill.exec.record.AbstractRecordBatch.next():186
> org.apache.drill.exec.record.AbstractRecordBatch.next():126
> org.apache.drill.exec.record.AbstractRecordBatch.next():116
> org.apache.drill.exec.record.AbstractUnaryRecordBatch.innerNext():63
> org.apache.drill.exec.record.AbstractRecordBatch.next():186
> org.apache.drill.exec.record.AbstractRecordBatch.next():126
> org.apache.drill.exec.record.AbstractRecordBatch.next():116
> org.apache.drill.exec.record.AbstractUnaryRecordBatch.innerNext():63
> 
> org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.innerNext():141
> org.apache.drill.exec.record.AbstractRecordBatch.next():186
> org.apache.drill.exec.physical.impl.BaseRootExec.next():104
> 
> org.apache.drill.exec.physical.impl.ScreenCreator$ScreenRoot.innerNext():83
> org.apache.drill.exec.physical.impl.BaseRootExec.next():94
> org.apache.drill.exec.work.fragment.FragmentExecutor$1.run():296
> org.apache.drill.exec.work.fragment.FragmentExecutor$1.run():283
> ...():0
> org.apache.hadoop.security.UserGroupInformation.doAs():1746
> org.apache.drill.exec.work.fragment.FragmentExecutor.run():283
> org.apache.drill.common.SelfCleaningRunnable.run():38
> ...():0
> {noformat}
> *Actual result:* The exception message is inadequate:
> {noformat}
> org.apache.drill.common.exceptions.UserRemoteException: EXECUTION_ERROR 
> ERROR: Table schema must have exactly one column.
> Exception thrown from 
> org.apache.drill.exec.physical.impl.scan.ScanOperatorExec
> Fragment 0:0
> [Error Id: a76a1576-419a-413f-840f-088157167a6d on userf87d-pc:31010]
>   (java.lang.IllegalStateException) Table schema must have exactly one column.
> 
> org.apache.drill.exec.physical.impl.scan.columns.ColumnsArrayManager.resolveColumn():108
> 
> org.apache.drill.exec.physical.impl.scan.project.ReaderLevelProjection.resolveSpecial():91
> 
> org.apache.drill.exec.physical.impl.scan.project.ExplicitSchemaProjection.resolveRootTuple():62
> 
> org.apache.drill.exec.physical.impl.scan.project.ExplicitSchemaProjection.():52
> 
> org.apache.drill.exec.physical.impl.scan.project.ReaderSchemaOrchestrator.doExplicitProjection():223
> 
> org.apache.drill.exec.physical.impl.scan.project.ReaderSchemaOrchestrator.reviseOutputProjection():155
> 
> 

[jira] [Commented] (DRILL-7179) Compiling drill from source doesn't include all the jars in the distribution/target dir

2019-04-15 Thread Hefei Li (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818587#comment-16818587
 ] 

Hefei Li commented on DRILL-7179:
-

[~gperp] Can you tell me the branch and version you compiled, and the compiled 
log information?

> Compiling drill from source doesn't include all the jars in the 
> distribution/target dir
> ---
>
> Key: DRILL-7179
> URL: https://issues.apache.org/jira/browse/DRILL-7179
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Building on Windows 10
>Reporter: Georgi Genchev Perpeliev
>Assignee: Hefei Li
>Priority: Minor
>
> Following the instructions on 
> [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with 
> incomplete tarball including only drill-shaded-guava-23.0.jar in the jars 
> subdirectory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DRILL-7179) Compiling drill from source doesn't include all the jars in the distribution/target dir

2019-04-15 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li reassigned DRILL-7179:
---

Assignee: Hefei Li

> Compiling drill from source doesn't include all the jars in the 
> distribution/target dir
> ---
>
> Key: DRILL-7179
> URL: https://issues.apache.org/jira/browse/DRILL-7179
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.15.0
> Environment: Building on Windows 10
>Reporter: Georgi Genchev Perpeliev
>Assignee: Hefei Li
>Priority: Minor
>
> Following the instructions on 
> [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with 
> incomplete tarball including only drill-shaded-guava-23.0.jar in the jars 
> subdirectory.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (DRILL-7161) Aggregation with group by clause

2019-04-10 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li resolved DRILL-7161.
-
   Resolution: Not A Bug
Fix Version/s: 1.14.0

By default, Drill does not support different types of JSON lists. For support 
on JSON data types, you can refer to the **[JSON Data 
Model|https://drill.apache.org/docs/json-data-model/].

In this case, the ‘B’ column in your given test data is all null.
When Drill reads the column, it will be processed by default according to the 
VARCHAR type.
So, if you want to work with numeric types as you expect, you can use the 
[CAST|https://drill.apache.org/docs/data-type-conversion/] type conversion 
function provided by Drill.

Such as:
{code:java}
select a, sum(CAST(b as INT)) from dfs.`/drill/data/sample.json` group by a
{code}

Then it will work fine.

> Aggregation with group by clause
> 
>
> Key: DRILL-7161
> URL: https://issues.apache.org/jira/browse/DRILL-7161
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Functions - Drill
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Assignee: Hefei Li
>Priority: Blocker
>  Labels: Drill, issue
> Fix For: 1.14.0
>
>
> Facing some issues with the following case:
> Json file (*sample.json*) is having the following content:
> {"a":2,"b":null}
> {"a":2,"b":null}
> {"a":3,"b":null}
> {"a":4,"b":null}
> *Query:*
> SELECT a, sum(b) FROM dfs.`C:\\Users\\user\\Desktop\\sample.json` group by a;
> *Error:*
> UNSUPPORTED_OPERATION ERROR: Only COUNT, MIN and MAX aggregate functions 
> supported for VarChar type
> *Observation:*
> If we query without using group by, then it is working fine without any 
> error. If group by is used, then sum of null values is throwing the above 
> error.
>  
> Can anyone please let us know the solution for this or if there are any 
> alternative.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Issue Comment Deleted] (DRILL-7161) Aggregation with group by clause

2019-04-10 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li updated DRILL-7161:

Comment: was deleted

(was: By default, Drill does not support different types of JSON lists. For 
support on JSON data types, you can refer to the *[JSON Data 
Model|[https://drill.apache.org/docs/json-data-model/]]*.

In this case, the ‘B’ column in your given test data is all null.
When Drill reads the column, it will be processed by default according to the 
VARCHAR type.
So, if you want to work with numeric types as you expect, you can use the 
*[CAST|[https://drill.apache.org/docs/data-type-conversion/]]* type conversion 
function provided by Drill.

Such as:
{code:java}
select a, sum(CAST(b as INT)) from dfs.`/drill/data/sample.json`  group by a
{code}
Then it will work fine.)

> Aggregation with group by clause
> 
>
> Key: DRILL-7161
> URL: https://issues.apache.org/jira/browse/DRILL-7161
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Functions - Drill
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Assignee: Hefei Li
>Priority: Blocker
>  Labels: Drill, issue
>
> Facing some issues with the following case:
> Json file (*sample.json*) is having the following content:
> {"a":2,"b":null}
> {"a":2,"b":null}
> {"a":3,"b":null}
> {"a":4,"b":null}
> *Query:*
> SELECT a, sum(b) FROM dfs.`C:\\Users\\user\\Desktop\\sample.json` group by a;
> *Error:*
> UNSUPPORTED_OPERATION ERROR: Only COUNT, MIN and MAX aggregate functions 
> supported for VarChar type
> *Observation:*
> If we query without using group by, then it is working fine without any 
> error. If group by is used, then sum of null values is throwing the above 
> error.
>  
> Can anyone please let us know the solution for this or if there are any 
> alternative.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (DRILL-7161) Aggregation with group by clause

2019-04-10 Thread Hefei Li (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814223#comment-16814223
 ] 

Hefei Li commented on DRILL-7161:
-

By default, Drill does not support different types of JSON lists. For support 
on JSON data types, you can refer to the *[JSON Data 
Model|[https://drill.apache.org/docs/json-data-model/]]*.

In this case, the ‘B’ column in your given test data is all null.
When Drill reads the column, it will be processed by default according to the 
VARCHAR type.
So, if you want to work with numeric types as you expect, you can use the 
*[CAST|[https://drill.apache.org/docs/data-type-conversion/]]* type conversion 
function provided by Drill.

Such as:
{code:java}
select a, sum(CAST(b as INT)) from dfs.`/drill/data/sample.json`  group by a
{code}
Then it will work fine.

> Aggregation with group by clause
> 
>
> Key: DRILL-7161
> URL: https://issues.apache.org/jira/browse/DRILL-7161
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Functions - Drill
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Assignee: Hefei Li
>Priority: Blocker
>  Labels: Drill, issue
>
> Facing some issues with the following case:
> Json file (*sample.json*) is having the following content:
> {"a":2,"b":null}
> {"a":2,"b":null}
> {"a":3,"b":null}
> {"a":4,"b":null}
> *Query:*
> SELECT a, sum(b) FROM dfs.`C:\\Users\\user\\Desktop\\sample.json` group by a;
> *Error:*
> UNSUPPORTED_OPERATION ERROR: Only COUNT, MIN and MAX aggregate functions 
> supported for VarChar type
> *Observation:*
> If we query without using group by, then it is working fine without any 
> error. If group by is used, then sum of null values is throwing the above 
> error.
>  
> Can anyone please let us know the solution for this or if there are any 
> alternative.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DRILL-7161) Aggregation with group by clause

2019-04-10 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li reassigned DRILL-7161:
---

Assignee: Hefei Li

> Aggregation with group by clause
> 
>
> Key: DRILL-7161
> URL: https://issues.apache.org/jira/browse/DRILL-7161
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Functions - Drill
>Affects Versions: 1.14.0
>Reporter: Gayathri
>Assignee: Hefei Li
>Priority: Blocker
>  Labels: Drill, issue
>
> Facing some issues with the following case:
> Json file (*sample.json*) is having the following content:
> {"a":2,"b":null}
> {"a":2,"b":null}
> {"a":3,"b":null}
> {"a":4,"b":null}
> *Query:*
> SELECT a, sum(b) FROM dfs.`C:\\Users\\user\\Desktop\\sample.json` group by a;
> *Error:*
> UNSUPPORTED_OPERATION ERROR: Only COUNT, MIN and MAX aggregate functions 
> supported for VarChar type
> *Observation:*
> If we query without using group by, then it is working fine without any 
> error. If group by is used, then sum of null values is throwing the above 
> error.
>  
> Can anyone please let us know the solution for this or if there are any 
> alternative.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DRILL-5239) Drill text reader reports wrong results when column value starts with '#'

2019-04-08 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li reassigned DRILL-5239:
---

Assignee: (was: Hefei Li)

> Drill text reader reports wrong results when column value starts with '#'
> -
>
> Key: DRILL-5239
> URL: https://issues.apache.org/jira/browse/DRILL-5239
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - Text  CSV
>Affects Versions: 1.10.0
>Reporter: Rahul Challapalli
>Priority: Blocker
>  Labels: doc-impacting
> Fix For: Future
>
>
> git.commit.id.abbrev=2af709f
> Data Set :
> {code}
> D|32
> 8h|234
> ;#|3489
> ^$*(|308
> #|98
> {code}
> Wrong Result : (Last row is missing)
> {code}
> select columns[0] as col1, columns[1] as col2 from 
> dfs.`/drill/testdata/wtf2.tbl`;
> +---+---+
> | col1  | col2  |
> +---+---+
> | D | 32|
> | 8h| 234   |
> | ;#| 3489  |
> | ^$*(  | 308   |
> +---+---+
> 4 rows selected (0.233 seconds)
> {code}
> The issue does not however happen with a parquet file



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DRILL-5239) Drill text reader reports wrong results when column value starts with '#'

2019-04-04 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li reassigned DRILL-5239:
---

Assignee: Hefei Li

> Drill text reader reports wrong results when column value starts with '#'
> -
>
> Key: DRILL-5239
> URL: https://issues.apache.org/jira/browse/DRILL-5239
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - Text  CSV
>Affects Versions: 1.10.0
>Reporter: Rahul Challapalli
>Assignee: Hefei Li
>Priority: Blocker
>  Labels: doc-impacting
> Fix For: Future
>
>
> git.commit.id.abbrev=2af709f
> Data Set :
> {code}
> D|32
> 8h|234
> ;#|3489
> ^$*(|308
> #|98
> {code}
> Wrong Result : (Last row is missing)
> {code}
> select columns[0] as col1, columns[1] as col2 from 
> dfs.`/drill/testdata/wtf2.tbl`;
> +---+---+
> | col1  | col2  |
> +---+---+
> | D | 32|
> | 8h| 234   |
> | ;#| 3489  |
> | ^$*(  | 308   |
> +---+---+
> 4 rows selected (0.233 seconds)
> {code}
> The issue does not however happen with a parquet file



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DRILL-7067) Querying parquet file with null value field error

2019-04-04 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li reassigned DRILL-7067:
---

Assignee: (was: Hefei Li)

> Querying parquet file with null value field error
> -
>
> Key: DRILL-7067
> URL: https://issues.apache.org/jira/browse/DRILL-7067
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - Parquet
>Affects Versions: 1.15.0
> Environment: Ubuntu 18.04.1 LTS 
> Apache Drill 1.15.0 
>Reporter: Jardhel Cachola
>Priority: Blocker
> Fix For: Future
>
>
> When we try to join two parquet tables and one of them has null values on any 
> field, the query doesn't run. It fails showing the following error: 
> Error: SYSTEM ERROR: IllegalStateException: Failure while reading vector. 
> Expected vector class of org.apache.drill.exec.vector.NullableIntVector but 
> was holding vector class 
> org.apache.drill.exec.vector.NullableVarDecimalVector, field= [`id_hubbles` 
> (VARDECIMAL(38, 4):OPTIONAL), children=([`$bits$` (UINT1:REQUIRED)], 
> [`id_hubbles` (VARDECIMAL(38, 4):OPTIONAL), children=([`$offsets$` 
> (UINT4:REQUIRED)])])]
> Fragment 2:0
> Please, refer to logs for more information.
> [Error Id: 48f63255-c771-4809-8252-ef7a78fda31b on 
> |]
> (java.lang.IllegalStateException) Failure while reading vector. Expected 
> vector class of org.apache.drill.exec.vector.NullableIntVector but was 
> holding vector class org.apache.drill.exec.vector.NullableVarDecimalVector, 
> field= [`id_hubbles` (VARDECIMAL(38, 4):OPTIONAL), children=([`$bits$` 
> (UINT1:REQUIRED)], [`id_hubbles` (VARDECIMAL(38, 4):OPTIONAL), 
> children=([`$offsets$` (UINT4:REQUIRED)])])] 
>  org.apache.drill.exec.record.VectorContainer.getValueAccessorById():324
>  org.apache.drill.exec.record.RecordBatchLoader.getValueAccessorById():251
>  
> org.apache.drill.exec.physical.impl.unorderedreceiver.UnorderedReceiverBatch.getValueAccessorById():142
>  
> org.apache.drill.exec.test.generated.PartitionerGen1732$OutgoingRecordBatch.doSetup():114
>  
> org.apache.drill.exec.test.generated.PartitionerGen1732$OutgoingRecordBatch.initializeBatch():399
>  
> org.apache.drill.exec.test.generated.PartitionerGen1732.flushOutgoingBatches():185
>  
> org.apache.drill.exec.physical.impl.partitionsender.PartitionerDecorator$FlushBatchesHandlingClass.execute():285
>  
> org.apache.drill.exec.physical.impl.partitionsender.PartitionerDecorator$PartitionerTask.run():340
>  java.util.concurrent.ThreadPoolExecutor.runWorker():1149
>  java.util.concurrent.ThreadPoolExecutor$Worker.run():624
>  java.lang.Thread.run():748 (state=,code=0)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Assigned] (DRILL-7067) Querying parquet file with null value field error

2019-04-04 Thread Hefei Li (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-7067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hefei Li reassigned DRILL-7067:
---

Assignee: Hefei Li

> Querying parquet file with null value field error
> -
>
> Key: DRILL-7067
> URL: https://issues.apache.org/jira/browse/DRILL-7067
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - Parquet
>Affects Versions: 1.15.0
> Environment: Ubuntu 18.04.1 LTS 
> Apache Drill 1.15.0 
>Reporter: Jardhel Cachola
>Assignee: Hefei Li
>Priority: Blocker
> Fix For: Future
>
>
> When we try to join two parquet tables and one of them has null values on any 
> field, the query doesn't run. It fails showing the following error: 
> Error: SYSTEM ERROR: IllegalStateException: Failure while reading vector. 
> Expected vector class of org.apache.drill.exec.vector.NullableIntVector but 
> was holding vector class 
> org.apache.drill.exec.vector.NullableVarDecimalVector, field= [`id_hubbles` 
> (VARDECIMAL(38, 4):OPTIONAL), children=([`$bits$` (UINT1:REQUIRED)], 
> [`id_hubbles` (VARDECIMAL(38, 4):OPTIONAL), children=([`$offsets$` 
> (UINT4:REQUIRED)])])]
> Fragment 2:0
> Please, refer to logs for more information.
> [Error Id: 48f63255-c771-4809-8252-ef7a78fda31b on 
> |]
> (java.lang.IllegalStateException) Failure while reading vector. Expected 
> vector class of org.apache.drill.exec.vector.NullableIntVector but was 
> holding vector class org.apache.drill.exec.vector.NullableVarDecimalVector, 
> field= [`id_hubbles` (VARDECIMAL(38, 4):OPTIONAL), children=([`$bits$` 
> (UINT1:REQUIRED)], [`id_hubbles` (VARDECIMAL(38, 4):OPTIONAL), 
> children=([`$offsets$` (UINT4:REQUIRED)])])] 
>  org.apache.drill.exec.record.VectorContainer.getValueAccessorById():324
>  org.apache.drill.exec.record.RecordBatchLoader.getValueAccessorById():251
>  
> org.apache.drill.exec.physical.impl.unorderedreceiver.UnorderedReceiverBatch.getValueAccessorById():142
>  
> org.apache.drill.exec.test.generated.PartitionerGen1732$OutgoingRecordBatch.doSetup():114
>  
> org.apache.drill.exec.test.generated.PartitionerGen1732$OutgoingRecordBatch.initializeBatch():399
>  
> org.apache.drill.exec.test.generated.PartitionerGen1732.flushOutgoingBatches():185
>  
> org.apache.drill.exec.physical.impl.partitionsender.PartitionerDecorator$FlushBatchesHandlingClass.execute():285
>  
> org.apache.drill.exec.physical.impl.partitionsender.PartitionerDecorator$PartitionerTask.run():340
>  java.util.concurrent.ThreadPoolExecutor.runWorker():1149
>  java.util.concurrent.ThreadPoolExecutor$Worker.run():624
>  java.lang.Thread.run():748 (state=,code=0)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)