Hi Volodymyr,
You are right, fancy join planning only makes sense if we have useful row and
key cardinality information.
I seem to recall that Drill estimated row counts based on file size. Clearly, a
10 MB file size has far fewer rows than a 1 GB file. Do we no longer do that
(or is my memory f
Hi Nicolas
Your maven command seems incomplete.
You need to navigate to the module containing the specific set of tests
(typically, for unit tests in Drill souce, it is the java-exec dir).
I dont think you need the 'install' phase of the lifecycle, and the 'test'
phase should be sufficient.
I am trying mvn install -Dtests=cluster -Pmapr but the tests does not run.
Any ideas?
At the same time, I am implementing the writing part of the plugin, I have
figured most of the components I need to implement out already. The only
thing that is still a bit obscure is around BatchCreator.
I hav
[
https://issues.apache.org/jira/browse/DRILL-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
salim achouche resolved DRILL-7276.
---
Resolution: Fixed
> xss(bug) in apache drill Web UI latest verion 1.16.0 when authenticated
sachouche merged pull request #1801: Merge 05 28 2019
URL: https://github.com/apache/drill/pull/1801
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
sachouche opened a new pull request #1801: Merge 05 28 2019
URL: https://github.com/apache/drill/pull/1801
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use t
sachouche closed pull request #1800: Batch committing read-to-commit changes up
to 05/28/2019
URL: https://github.com/apache/drill/pull/1800
This is an automated message from the Apache Git Service.
To respond to the message
sachouche opened a new pull request #1800: Batch committing read-to-commit
changes up to 05/28/2019
URL: https://github.com/apache/drill/pull/1800
This is an automated message from the Apache Git Service.
To respond to the m
sachouche closed pull request #1800: Batch committing read-to-commit changes up
to 05/28/2019
URL: https://github.com/apache/drill/pull/1800
This is an automated message from the Apache Git Service.
To respond to the message
Hi all,
Regarding the Impala's approach described by Paul, we have a similar thing
as Impala does: after applying LoptOptimizeJoinRule and other
optimizations, SwapHashJoinVisitor is applied to the rel nodes tree to swap
hash join inputs for some cases. It was implemented in the scope
of DRILL-223
Related work inn Iceberg. Worth a read :
https://docs.google.com/document/d/1Pk34C3diOfVCRc-sfxfhXZfzvxwum1Odo-6Jj9mwK38/edit#
On Tue, May 28, 2019 at 2:17 PM Aman Sinha wrote:
> The description I sent is for the planner but there's of course a run-time
> component which would consist of a 'Rec
sachouche opened a new pull request #1800: Batch committing read-to-commit
changes up to 05/28/2019
URL: https://github.com/apache/drill/pull/1800
This is an automated message from the Apache Git Service.
To respond to the m
Calcite's Programs.heuristicJoinOrder method with a bushy boolean
parameter. If the bushy parameter is true, it will choose
MultiJoinOptimizeBushyRule otherwise LoptOptimizeJoinRule. Glad to get
message that LoptOptimizeJoinRule could also produce the bushy tree
@Jinfeng.
On Wed, May 29, 2019 at 8
13 matches
Mail list logo