[jira] [Updated] (DRILL-7044) drill kudu query dose not support range + hash multilevel partition
[ https://issues.apache.org/jira/browse/DRILL-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fireapp updated DRILL-7044: --- Attachment: (was: 002.png) > drill kudu query dose not support range + hash multilevel partition > --- > > Key: DRILL-7044 > URL: https://issues.apache.org/jira/browse/DRILL-7044 > Project: Apache Drill > Issue Type: Bug > Components: Storage - Other >Affects Versions: 1.13.0, 1.14.0, 1.15.0 > Environment: drill : 1.13.0 > kudu : 1.8.0 >Reporter: fireapp >Priority: Critical > Labels: kudu > Attachments: 002.png, 003.png > > > drill kudu query dose not support range + hash multilevel partition > kudu table : > CREATE TABLE test1 ( > id int , > name string, > value string, > prmary key(id, name) > ), > PARTITION BY HASH (name) PARTITIONS 8, > PARTITION BY RANGE (id) ( > PARTITION 0 <= VALUES < 1, > PARTITION 1 <= VALUES < 2, > PARTITION 2 <= VALUES < 3, > PARTITION 3 <= VALUES < 4 > ); > and then insert 20002 rows into test1, but query not support. > query sql : select count(1) kudu.table_name, result : `No result found.` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7044) drill kudu query dose not support range + hash multilevel partition
[ https://issues.apache.org/jira/browse/DRILL-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fireapp updated DRILL-7044: --- Attachment: (was: 003.png) > drill kudu query dose not support range + hash multilevel partition > --- > > Key: DRILL-7044 > URL: https://issues.apache.org/jira/browse/DRILL-7044 > Project: Apache Drill > Issue Type: Bug > Components: Storage - Other >Affects Versions: 1.13.0, 1.14.0, 1.15.0 > Environment: drill : 1.13.0 > kudu : 1.8.0 >Reporter: fireapp >Priority: Critical > Labels: kudu > Attachments: 002.png, 003.png > > > drill kudu query dose not support range + hash multilevel partition > kudu table : > CREATE TABLE test1 ( > id int , > name string, > value string, > prmary key(id, name) > ), > PARTITION BY HASH (name) PARTITIONS 8, > PARTITION BY RANGE (id) ( > PARTITION 0 <= VALUES < 1, > PARTITION 1 <= VALUES < 2, > PARTITION 2 <= VALUES < 3, > PARTITION 3 <= VALUES < 4 > ); > and then insert 20002 rows into test1, but query not support. > query sql : select count(1) kudu.table_name, result : `No result found.` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7044) drill kudu query dose not support range + hash multilevel partition
[ https://issues.apache.org/jira/browse/DRILL-7044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fireapp updated DRILL-7044: --- Flags: Important Attachment: 003.png 002.png Labels: kudu (was: ) Priority: Critical (was: Major) Description: drill kudu query dose not support range + hash multilevel partition kudu table : CREATE TABLE test1 ( id int , name string, value string, prmary key(id, name) ), PARTITION BY HASH (name) PARTITIONS 8, PARTITION BY RANGE (id) ( PARTITION 0 <= VALUES < 1, PARTITION 1 <= VALUES < 2, PARTITION 2 <= VALUES < 3, PARTITION 3 <= VALUES < 4 ); and then insert 20002 rows into test1, but query not support. query sql : select count(1) kudu.table_name, result : `No result found.` was: drill kudu query dose not support range partition, query sql : select count(1) kudu.table_name, result : `No result found.` Summary: drill kudu query dose not support range + hash multilevel partition (was: drill kudu query dose not support range partition) > drill kudu query dose not support range + hash multilevel partition > --- > > Key: DRILL-7044 > URL: https://issues.apache.org/jira/browse/DRILL-7044 > Project: Apache Drill > Issue Type: Bug > Components: Storage - Other >Affects Versions: 1.13.0, 1.14.0, 1.15.0 > Environment: drill : 1.13.0 > kudu : 1.8.0 >Reporter: fireapp >Priority: Critical > Labels: kudu > Attachments: 002.png, 002.png, 003.png, 003.png > > > drill kudu query dose not support range + hash multilevel partition > kudu table : > CREATE TABLE test1 ( > id int , > name string, > value string, > prmary key(id, name) > ), > PARTITION BY HASH (name) PARTITIONS 8, > PARTITION BY RANGE (id) ( > PARTITION 0 <= VALUES < 1, > PARTITION 1 <= VALUES < 2, > PARTITION 2 <= VALUES < 3, > PARTITION 3 <= VALUES < 4 > ); > and then insert 20002 rows into test1, but query not support. > query sql : select count(1) kudu.table_name, result : `No result found.` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-7044) drill kudu query dose not support range partition
fireapp created DRILL-7044: -- Summary: drill kudu query dose not support range partition Key: DRILL-7044 URL: https://issues.apache.org/jira/browse/DRILL-7044 Project: Apache Drill Issue Type: Bug Components: Storage - Other Affects Versions: 1.15.0, 1.14.0, 1.13.0 Environment: drill : 1.13.0 kudu : 1.8.0 Reporter: fireapp Attachments: 002.png, 003.png drill kudu query dose not support range partition, query sql : select count(1) kudu.table_name, result : `No result found.` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-7043) Enhance Merge-Join to support Full Outer Join
[
https://issues.apache.org/jira/browse/DRILL-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772590#comment-16772590
]
Boaz Ben-Zvi commented on DRILL-7043:
-
This enhancement is becoming more useful as our storage begins to support
"sortedness" - e.g., Secondary Indexes, and future Parquet Metadata (e.g.,
taken from Hive).
> Enhance Merge-Join to support Full Outer Join
> -
>
> Key: DRILL-7043
> URL: https://issues.apache.org/jira/browse/DRILL-7043
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Relational Operators, Query Planning
> Optimization
>Affects Versions: 1.15.0
>Reporter: Boaz Ben-Zvi
>Assignee: Boaz Ben-Zvi
>Priority: Major
>
> Currently the Merge Join operator internally cannot support a Right Outer
> Join (and thus a Full Outer Join; for ROJ alone, the planner rotates the
> inputs and specifies a Left Outer Join).
> The actual reason for not supporting ROJ is the current MJ implementation
> - when a match is found, it puts a mark on the right side and iterates down
> on the right, resetting back at the end (and on to the next left side entry).
> This would create an ambiguity if the next left entry is bigger than the
> previous - is this an unmatched (i.e., need to return the right entry), or
> there was a prior match (i.e., just advance to the next right).
> Seems that adding a relevant flag to the persisted state ({{status}}) and
> some other code changes would make the operator support Right-Outer-Join as
> well (and thus a Full Outer Join). The planner need an update as well - to
> suggest the MJ in case of a FOJ, and maybe not to rotate the inputs in some
> MJ cases.
> Currently trying a FOJ with MJ (i.e. HJ disabled) produces the following
> "no plan found" from Calcite:
> {noformat}
> 0: jdbc:drill:zk=local> select * from temp t1 full outer join temp2 t2 on
> t1.d_date = t2.d_date;
> Error: SYSTEM ERROR: CannotPlanException: Node
> [rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]] could not be implemented;
> planner state:
> Root: rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]
> Original rel:
> DrillScreenRel(subset=[rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]]):
> rowcount = 6.0, cumulative cost = {0.6001 rows,
> 0.6001 cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 2802
> DrillProjectRel(subset=[rel#2801:Subset#7.LOGICAL.ANY([]).[]], **=[$0],
> **0=[$2]): rowcount = 6.0, cumulative cost = {6.0 rows, 12.0 cpu, 0.0 io, 0.0
> network, 0.0 memory}, id = 2800
> DrillJoinRel(subset=[rel#2799:Subset#6.LOGICAL.ANY([]).[]],
> condition=[=($1, $3)], joinType=[full]): rowcount = 6.0, cumulative cost =
> {10.0 rows, 104.0 cpu, 0.0 io, 0.0 network, 70.4 memory}, id = 2798
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (DRILL-7043) Enhance Merge-Join to support Full Outer Join
[
https://issues.apache.org/jira/browse/DRILL-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772590#comment-16772590
]
Boaz Ben-Zvi edited comment on DRILL-7043 at 2/20/19 3:32 AM:
--
This enhancement is becoming more useful as our storage begins to support
"sortedness" - e.g., Secondary Indexes, and future Parquet Metadata (e.g.,
taken from Hive). A Merge-Join on two sorted tables always out-performs a
Hash-Join.
was (Author: ben-zvi):
This enhancement is becoming more useful as our storage begins to support
"sortedness" - e.g., Secondary Indexes, and future Parquet Metadata (e.g.,
taken from Hive).
> Enhance Merge-Join to support Full Outer Join
> -
>
> Key: DRILL-7043
> URL: https://issues.apache.org/jira/browse/DRILL-7043
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Relational Operators, Query Planning
> Optimization
>Affects Versions: 1.15.0
>Reporter: Boaz Ben-Zvi
>Assignee: Boaz Ben-Zvi
>Priority: Major
>
> Currently the Merge Join operator internally cannot support a Right Outer
> Join (and thus a Full Outer Join; for ROJ alone, the planner rotates the
> inputs and specifies a Left Outer Join).
> The actual reason for not supporting ROJ is the current MJ implementation
> - when a match is found, it puts a mark on the right side and iterates down
> on the right, resetting back at the end (and on to the next left side entry).
> This would create an ambiguity if the next left entry is bigger than the
> previous - is this an unmatched (i.e., need to return the right entry), or
> there was a prior match (i.e., just advance to the next right).
> Seems that adding a relevant flag to the persisted state ({{status}}) and
> some other code changes would make the operator support Right-Outer-Join as
> well (and thus a Full Outer Join). The planner need an update as well - to
> suggest the MJ in case of a FOJ, and maybe not to rotate the inputs in some
> MJ cases.
> Currently trying a FOJ with MJ (i.e. HJ disabled) produces the following
> "no plan found" from Calcite:
> {noformat}
> 0: jdbc:drill:zk=local> select * from temp t1 full outer join temp2 t2 on
> t1.d_date = t2.d_date;
> Error: SYSTEM ERROR: CannotPlanException: Node
> [rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]] could not be implemented;
> planner state:
> Root: rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]
> Original rel:
> DrillScreenRel(subset=[rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]]):
> rowcount = 6.0, cumulative cost = {0.6001 rows,
> 0.6001 cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 2802
> DrillProjectRel(subset=[rel#2801:Subset#7.LOGICAL.ANY([]).[]], **=[$0],
> **0=[$2]): rowcount = 6.0, cumulative cost = {6.0 rows, 12.0 cpu, 0.0 io, 0.0
> network, 0.0 memory}, id = 2800
> DrillJoinRel(subset=[rel#2799:Subset#6.LOGICAL.ANY([]).[]],
> condition=[=($1, $3)], joinType=[full]): rowcount = 6.0, cumulative cost =
> {10.0 rows, 104.0 cpu, 0.0 io, 0.0 network, 70.4 memory}, id = 2798
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-7043) Enhance Merge-Join to support Full Outer Join
[
https://issues.apache.org/jira/browse/DRILL-7043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16772589#comment-16772589
]
Boaz Ben-Zvi commented on DRILL-7043:
-
Possible relevant other Jiras: DRILL-1059 (No FOJ with HJ disabled; though it
shows a different error) and DRILL-4811 (TPCDS 51 - FOJ not supported).
> Enhance Merge-Join to support Full Outer Join
> -
>
> Key: DRILL-7043
> URL: https://issues.apache.org/jira/browse/DRILL-7043
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Relational Operators, Query Planning
> Optimization
>Affects Versions: 1.15.0
>Reporter: Boaz Ben-Zvi
>Assignee: Boaz Ben-Zvi
>Priority: Major
>
> Currently the Merge Join operator internally cannot support a Right Outer
> Join (and thus a Full Outer Join; for ROJ alone, the planner rotates the
> inputs and specifies a Left Outer Join).
> The actual reason for not supporting ROJ is the current MJ implementation
> - when a match is found, it puts a mark on the right side and iterates down
> on the right, resetting back at the end (and on to the next left side entry).
> This would create an ambiguity if the next left entry is bigger than the
> previous - is this an unmatched (i.e., need to return the right entry), or
> there was a prior match (i.e., just advance to the next right).
> Seems that adding a relevant flag to the persisted state ({{status}}) and
> some other code changes would make the operator support Right-Outer-Join as
> well (and thus a Full Outer Join). The planner need an update as well - to
> suggest the MJ in case of a FOJ, and maybe not to rotate the inputs in some
> MJ cases.
> Currently trying a FOJ with MJ (i.e. HJ disabled) produces the following
> "no plan found" from Calcite:
> {noformat}
> 0: jdbc:drill:zk=local> select * from temp t1 full outer join temp2 t2 on
> t1.d_date = t2.d_date;
> Error: SYSTEM ERROR: CannotPlanException: Node
> [rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]] could not be implemented;
> planner state:
> Root: rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]
> Original rel:
> DrillScreenRel(subset=[rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]]):
> rowcount = 6.0, cumulative cost = {0.6001 rows,
> 0.6001 cpu, 0.0 io, 0.0 network, 0.0 memory}, id = 2802
> DrillProjectRel(subset=[rel#2801:Subset#7.LOGICAL.ANY([]).[]], **=[$0],
> **0=[$2]): rowcount = 6.0, cumulative cost = {6.0 rows, 12.0 cpu, 0.0 io, 0.0
> network, 0.0 memory}, id = 2800
> DrillJoinRel(subset=[rel#2799:Subset#6.LOGICAL.ANY([]).[]],
> condition=[=($1, $3)], joinType=[full]): rowcount = 6.0, cumulative cost =
> {10.0 rows, 104.0 cpu, 0.0 io, 0.0 network, 70.4 memory}, id = 2798
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-7043) Enhance Merge-Join to support Full Outer Join
Boaz Ben-Zvi created DRILL-7043:
---
Summary: Enhance Merge-Join to support Full Outer Join
Key: DRILL-7043
URL: https://issues.apache.org/jira/browse/DRILL-7043
Project: Apache Drill
Issue Type: Improvement
Components: Execution - Relational Operators, Query Planning
Optimization
Affects Versions: 1.15.0
Reporter: Boaz Ben-Zvi
Assignee: Boaz Ben-Zvi
Currently the Merge Join operator internally cannot support a Right Outer
Join (and thus a Full Outer Join; for ROJ alone, the planner rotates the inputs
and specifies a Left Outer Join).
The actual reason for not supporting ROJ is the current MJ implementation -
when a match is found, it puts a mark on the right side and iterates down on
the right, resetting back at the end (and on to the next left side entry).
This would create an ambiguity if the next left entry is bigger than the
previous - is this an unmatched (i.e., need to return the right entry), or
there was a prior match (i.e., just advance to the next right).
Seems that adding a relevant flag to the persisted state ({{status}}) and
some other code changes would make the operator support Right-Outer-Join as
well (and thus a Full Outer Join). The planner need an update as well - to
suggest the MJ in case of a FOJ, and maybe not to rotate the inputs in some MJ
cases.
Currently trying a FOJ with MJ (i.e. HJ disabled) produces the following "no
plan found" from Calcite:
{noformat}
0: jdbc:drill:zk=local> select * from temp t1 full outer join temp2 t2 on
t1.d_date = t2.d_date;
Error: SYSTEM ERROR: CannotPlanException: Node
[rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]] could not be implemented; planner
state:
Root: rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]
Original rel:
DrillScreenRel(subset=[rel#2804:Subset#8.PHYSICAL.SINGLETON([]).[]]): rowcount
= 6.0, cumulative cost = {0.6001 rows, 0.6001 cpu, 0.0
io, 0.0 network, 0.0 memory}, id = 2802
DrillProjectRel(subset=[rel#2801:Subset#7.LOGICAL.ANY([]).[]], **=[$0],
**0=[$2]): rowcount = 6.0, cumulative cost = {6.0 rows, 12.0 cpu, 0.0 io, 0.0
network, 0.0 memory}, id = 2800
DrillJoinRel(subset=[rel#2799:Subset#6.LOGICAL.ANY([]).[]],
condition=[=($1, $3)], joinType=[full]): rowcount = 6.0, cumulative cost =
{10.0 rows, 104.0 cpu, 0.0 io, 0.0 network, 70.4 memory}, id = 2798
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-2010) merge join returns wrong number of rows with large dataset
[
https://issues.apache.org/jira/browse/DRILL-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boaz Ben-Zvi closed DRILL-2010.
---
Resolution: Cannot Reproduce
Fix Version/s: 1.15.0
Retested the same test - work for me. Looks like later changes in
{{RecordIterator}} made the code work correctly across multiple (right side)
batches.
> merge join returns wrong number of rows with large dataset
> --
>
> Key: DRILL-2010
> URL: https://issues.apache.org/jira/browse/DRILL-2010
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Relational Operators
>Affects Versions: 0.8.0
>Reporter: Chun Chang
>Assignee: Boaz Ben-Zvi
>Priority: Critical
> Fix For: 1.15.0
>
> Attachments: DRILL-2010-1.patch, DRILL-2010-1.patch
>
>
> #Mon Jan 12 18:19:31 EST 2015
> git.commit.id.abbrev=5b012bf
> When data set is big enough (like larger than one batch size), merge join
> will not returns the correct number of rows. Hash join returns the correct
> number of rows. Data can be downloaded from:
> https://s3.amazonaws.com/apache-drill/files/complex100k.json.gz
> With this dataset, the following query should return 10,000,000.
> {code}
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> alter session set
> `planner.enable_mergejoin` = true;
> +++
> | ok | summary |
> +++
> | true | planner.enable_mergejoin updated. |
> +++
> 1 row selected (0.024 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> alter session set
> `planner.enable_hashjoin` = false;
> +++
> | ok | summary |
> +++
> | true | planner.enable_hashjoin updated. |
> +++
> 1 row selected (0.024 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> select count(a.id) from
> `complex100k.json` a inner join `complex100k.json` b on a.gbyi=b.gbyi;
> ++
> | EXPR$0 |
> ++
> | 9046760|
> ++
> 1 row selected (6.205 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> alter session set
> `planner.enable_mergejoin` = false;
> +++
> | ok | summary |
> +++
> | true | planner.enable_mergejoin updated. |
> +++
> 1 row selected (0.026 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> alter session set
> `planner.enable_hashjoin` = true;
> +++
> | ok | summary |
> +++
> | true | planner.enable_hashjoin updated. |
> +++
> 1 row selected (0.024 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> select count(a.id) from
> `complex100k.json` a inner join `complex100k.json` b on a.gbyi=b.gbyi;
> ++
> | EXPR$0 |
> ++
> | 1000 |
> ++
> 1 row selected (4.453 seconds)
> {code}
> With smaller dataset, both merge and hash join returns the same correct
> number.
> physical plan for merge join:
> {code}
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> explain plan for select
> count(a.id) from `complex100k.json` a inner join `complex100k.json` b on
> a.gbyi=b.gbyi;
> +++
> |text|json|
> +++
> | 00-00Screen
> 00-01 StreamAgg(group=[{}], EXPR$0=[COUNT($0)])
> 00-02Project(id=[$1])
> 00-03 MergeJoin(condition=[=($0, $2)], joinType=[inner])
> 00-05SelectionVectorRemover
> 00-07 Sort(sort0=[$0], dir0=[ASC])
> 00-09Scan(groupscan=[EasyGroupScan
> [selectionRoot=/drill/testdata/complex_type/json/complex100k.json,
> numFiles=1, columns=[`gbyi`, `id`],
> files=[maprfs:/drill/testdata/complex_type/json/complex100k.json]]])
> 00-04Project(gbyi0=[$0])
> 00-06 SelectionVectorRemover
> 00-08Sort(sort0=[$0], dir0=[ASC])
> 00-10 Scan(groupscan=[EasyGroupScan
> [selectionRoot=/drill/testdata/complex_type/json/complex100k.json,
> numFiles=1, columns=[`gbyi`],
> files=[maprfs:/drill/testdata/complex_type/json/complex100k.json]]])
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DRILL-2010) merge join returns wrong number of rows with large dataset
[
https://issues.apache.org/jira/browse/DRILL-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boaz Ben-Zvi reassigned DRILL-2010:
---
Assignee: Boaz Ben-Zvi
> merge join returns wrong number of rows with large dataset
> --
>
> Key: DRILL-2010
> URL: https://issues.apache.org/jira/browse/DRILL-2010
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Relational Operators
>Affects Versions: 0.8.0
>Reporter: Chun Chang
>Assignee: Boaz Ben-Zvi
>Priority: Critical
> Attachments: DRILL-2010-1.patch, DRILL-2010-1.patch
>
>
> #Mon Jan 12 18:19:31 EST 2015
> git.commit.id.abbrev=5b012bf
> When data set is big enough (like larger than one batch size), merge join
> will not returns the correct number of rows. Hash join returns the correct
> number of rows. Data can be downloaded from:
> https://s3.amazonaws.com/apache-drill/files/complex100k.json.gz
> With this dataset, the following query should return 10,000,000.
> {code}
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> alter session set
> `planner.enable_mergejoin` = true;
> +++
> | ok | summary |
> +++
> | true | planner.enable_mergejoin updated. |
> +++
> 1 row selected (0.024 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> alter session set
> `planner.enable_hashjoin` = false;
> +++
> | ok | summary |
> +++
> | true | planner.enable_hashjoin updated. |
> +++
> 1 row selected (0.024 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> select count(a.id) from
> `complex100k.json` a inner join `complex100k.json` b on a.gbyi=b.gbyi;
> ++
> | EXPR$0 |
> ++
> | 9046760|
> ++
> 1 row selected (6.205 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> alter session set
> `planner.enable_mergejoin` = false;
> +++
> | ok | summary |
> +++
> | true | planner.enable_mergejoin updated. |
> +++
> 1 row selected (0.026 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> alter session set
> `planner.enable_hashjoin` = true;
> +++
> | ok | summary |
> +++
> | true | planner.enable_hashjoin updated. |
> +++
> 1 row selected (0.024 seconds)
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> select count(a.id) from
> `complex100k.json` a inner join `complex100k.json` b on a.gbyi=b.gbyi;
> ++
> | EXPR$0 |
> ++
> | 1000 |
> ++
> 1 row selected (4.453 seconds)
> {code}
> With smaller dataset, both merge and hash join returns the same correct
> number.
> physical plan for merge join:
> {code}
> 0: jdbc:drill:schema=dfs.drillTestDirComplexJ> explain plan for select
> count(a.id) from `complex100k.json` a inner join `complex100k.json` b on
> a.gbyi=b.gbyi;
> +++
> |text|json|
> +++
> | 00-00Screen
> 00-01 StreamAgg(group=[{}], EXPR$0=[COUNT($0)])
> 00-02Project(id=[$1])
> 00-03 MergeJoin(condition=[=($0, $2)], joinType=[inner])
> 00-05SelectionVectorRemover
> 00-07 Sort(sort0=[$0], dir0=[ASC])
> 00-09Scan(groupscan=[EasyGroupScan
> [selectionRoot=/drill/testdata/complex_type/json/complex100k.json,
> numFiles=1, columns=[`gbyi`, `id`],
> files=[maprfs:/drill/testdata/complex_type/json/complex100k.json]]])
> 00-04Project(gbyi0=[$0])
> 00-06 SelectionVectorRemover
> 00-08Sort(sort0=[$0], dir0=[ASC])
> 00-10 Scan(groupscan=[EasyGroupScan
> [selectionRoot=/drill/testdata/complex_type/json/complex100k.json,
> numFiles=1, columns=[`gbyi`],
> files=[maprfs:/drill/testdata/complex_type/json/complex100k.json]]])
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6582) SYSLOG (RFC-5424) Format Plugin
[ https://issues.apache.org/jira/browse/DRILL-6582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6582: --- Labels: doc-impacting ready-to-commit (was: doc-impacting) > SYSLOG (RFC-5424) Format Plugin > --- > > Key: DRILL-6582 > URL: https://issues.apache.org/jira/browse/DRILL-6582 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: Future >Reporter: Charles Givre >Assignee: Charles Givre >Priority: Major > Labels: doc-impacting, ready-to-commit > Fix For: 1.16.0 > > > Many security log files are in the format defined by RFC-5424. A format > plugin which can read data formatted in according to this specification would > be very useful for security engineers as well as network engineers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7042) DRILL: Apache drill v1.15.0 failed to generate deb/rpm package
[ https://issues.apache.org/jira/browse/DRILL-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pritesh Maker updated DRILL-7042: - Fix Version/s: (was: Future) 1.16.0 > DRILL: Apache drill v1.15.0 failed to generate deb/rpm package > -- > > Key: DRILL-7042 > URL: https://issues.apache.org/jira/browse/DRILL-7042 > Project: Apache Drill > Issue Type: Improvement > Components: Tools, Build Test >Affects Versions: 1.15.0 > Environment: Ubuntu/Debian/CentOS installed on ARM64 server machine. >Reporter: Naresh Bhat >Priority: Major > Fix For: 1.16.0 > > > I tried to create a debian/rpm package on ARM64 machine, But it failed to > generate the debian/rpm package on Ubuntu/CentOS machine. It is required to > fix the pom.xml file under distribution folder. > Error logs while generating DEB package: > = > drill$ git branch > master > * v1.15.0 > drill$ mvn clean -X package -Pdeb -DskipTests > . > .. > [INFO] Creating debian package: target/drill-1.15.0.deb > [INFO] Building data > [ERROR] Failed to create debian package target/drill-1.15.0.deb > org.vafer.jdeb.PackagingException: Failed to create debian package > target/drill-1.15.0.deb > at org.vafer.jdeb.maven.DebMaker.makeDeb (DebMaker.java:247) > at org.vafer.jdeb.maven.DebMojo.execute (DebMojo.java:416) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:356) > Caused by: org.vafer.jdeb.PackagingException: Could not create deb package > at org.vafer.jdeb.Processor.createDeb (Processor.java:172) > at org.vafer.jdeb.maven.DebMaker.makeDeb (DebMaker.java:244) > at org.vafer.jdeb.maven.DebMojo.execute (DebMojo.java:416) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) >
[jira] [Assigned] (DRILL-7042) DRILL: Apache drill v1.15.0 failed to generate deb/rpm package
[ https://issues.apache.org/jira/browse/DRILL-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pritesh Maker reassigned DRILL-7042: Assignee: Naresh Bhat > DRILL: Apache drill v1.15.0 failed to generate deb/rpm package > -- > > Key: DRILL-7042 > URL: https://issues.apache.org/jira/browse/DRILL-7042 > Project: Apache Drill > Issue Type: Improvement > Components: Tools, Build Test >Affects Versions: 1.15.0 > Environment: Ubuntu/Debian/CentOS installed on ARM64 server machine. >Reporter: Naresh Bhat >Assignee: Naresh Bhat >Priority: Major > Fix For: 1.16.0 > > > I tried to create a debian/rpm package on ARM64 machine, But it failed to > generate the debian/rpm package on Ubuntu/CentOS machine. It is required to > fix the pom.xml file under distribution folder. > Error logs while generating DEB package: > = > drill$ git branch > master > * v1.15.0 > drill$ mvn clean -X package -Pdeb -DskipTests > . > .. > [INFO] Creating debian package: target/drill-1.15.0.deb > [INFO] Building data > [ERROR] Failed to create debian package target/drill-1.15.0.deb > org.vafer.jdeb.PackagingException: Failed to create debian package > target/drill-1.15.0.deb > at org.vafer.jdeb.maven.DebMaker.makeDeb (DebMaker.java:247) > at org.vafer.jdeb.maven.DebMojo.execute (DebMojo.java:416) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:356) > Caused by: org.vafer.jdeb.PackagingException: Could not create deb package > at org.vafer.jdeb.Processor.createDeb (Processor.java:172) > at org.vafer.jdeb.maven.DebMaker.makeDeb (DebMaker.java:244) > at org.vafer.jdeb.maven.DebMojo.execute (DebMojo.java:416) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) >
[jira] [Updated] (DRILL-7042) DRILL: Apache drill v1.15.0 failed to generate deb/rpm package
[ https://issues.apache.org/jira/browse/DRILL-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pritesh Maker updated DRILL-7042: - Reviewer: Vitalii Diravka > DRILL: Apache drill v1.15.0 failed to generate deb/rpm package > -- > > Key: DRILL-7042 > URL: https://issues.apache.org/jira/browse/DRILL-7042 > Project: Apache Drill > Issue Type: Improvement > Components: Tools, Build Test >Affects Versions: 1.15.0 > Environment: Ubuntu/Debian/CentOS installed on ARM64 server machine. >Reporter: Naresh Bhat >Assignee: Naresh Bhat >Priority: Major > Fix For: 1.16.0 > > > I tried to create a debian/rpm package on ARM64 machine, But it failed to > generate the debian/rpm package on Ubuntu/CentOS machine. It is required to > fix the pom.xml file under distribution folder. > Error logs while generating DEB package: > = > drill$ git branch > master > * v1.15.0 > drill$ mvn clean -X package -Pdeb -DskipTests > . > .. > [INFO] Creating debian package: target/drill-1.15.0.deb > [INFO] Building data > [ERROR] Failed to create debian package target/drill-1.15.0.deb > org.vafer.jdeb.PackagingException: Failed to create debian package > target/drill-1.15.0.deb > at org.vafer.jdeb.maven.DebMaker.makeDeb (DebMaker.java:247) > at org.vafer.jdeb.maven.DebMojo.execute (DebMojo.java:416) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:356) > Caused by: org.vafer.jdeb.PackagingException: Could not create deb package > at org.vafer.jdeb.Processor.createDeb (Processor.java:172) > at org.vafer.jdeb.maven.DebMaker.makeDeb (DebMaker.java:244) > at org.vafer.jdeb.maven.DebMojo.execute (DebMojo.java:416) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) >
[jira] [Commented] (DRILL-7042) DRILL: Apache drill v1.15.0 failed to generate deb/rpm package
[ https://issues.apache.org/jira/browse/DRILL-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771747#comment-16771747 ] Naresh Bhat commented on DRILL-7042: I will appreciate, if you guys pull the same patch on master, and other development branches. > DRILL: Apache drill v1.15.0 failed to generate deb/rpm package > -- > > Key: DRILL-7042 > URL: https://issues.apache.org/jira/browse/DRILL-7042 > Project: Apache Drill > Issue Type: Improvement > Components: Tools, Build Test >Affects Versions: 1.15.0 > Environment: Ubuntu/Debian/CentOS installed on ARM64 server machine. >Reporter: Naresh Bhat >Priority: Major > Fix For: Future > > > I tried to create a debian/rpm package on ARM64 machine, But it failed to > generate the debian/rpm package on Ubuntu/CentOS machine. It is required to > fix the pom.xml file under distribution folder. > Error logs while generating DEB package: > = > drill$ git branch > master > * v1.15.0 > drill$ mvn clean -X package -Pdeb -DskipTests > . > .. > [INFO] Creating debian package: target/drill-1.15.0.deb > [INFO] Building data > [ERROR] Failed to create debian package target/drill-1.15.0.deb > org.vafer.jdeb.PackagingException: Failed to create debian package > target/drill-1.15.0.deb > at org.vafer.jdeb.maven.DebMaker.makeDeb (DebMaker.java:247) > at org.vafer.jdeb.maven.DebMojo.execute (DebMojo.java:416) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:192) > at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke > (NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:498) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced > (Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch > (Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:356) > Caused by: org.vafer.jdeb.PackagingException: Could not create deb package > at org.vafer.jdeb.Processor.createDeb (Processor.java:172) > at org.vafer.jdeb.maven.DebMaker.makeDeb (DebMaker.java:244) > at org.vafer.jdeb.maven.DebMojo.execute (DebMojo.java:416) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo > (DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) >
