Github user adeneche commented on a diff in the pull request:
https://github.com/apache/drill/pull/446#discussion_r57676038
--- Diff:
exec/rpc/src/main/java/org/apache/drill/exec/rpc/ProtobufLengthDecoder.java ---
@@ -82,15 +79,7 @@ protected void decode(ChannelHandlerContext ctx,
[
https://issues.apache.org/jira/browse/DRILL-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Khurram Faraaz resolved DRILL-4545.
---
Resolution: Invalid
> Incorrect query plan for LIMIT 0 query
> ---
If a fragment has already begun execution and sent some data to downstream
fragments, there is no way to simply restart the failed fragment, because
we would also have to restart any downstream fragments that consumed that
output, and so on up the tree, as well as restart any leaf fragments that
fe
We actually removed the concept of a distributed cache from drill
altogether. So currently nothing is replacing HazelCast.
The distributed cache was used for storing the initialization-data for
intermediate fragments. Only leaf node fragments were sent via the RPC
layer. But the distributed cache
[
https://issues.apache.org/jira/browse/DRILL-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venki Korukanti resolved DRILL-4549.
Resolution: Fixed
> Add support for more truncation units in date_trunc function
> -
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/450
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Venki Korukanti created DRILL-4550:
--
Summary: Add support more time units in extract function
Key: DRILL-4550
URL: https://issues.apache.org/jira/browse/DRILL-4550
Project: Apache Drill
Issu
Github user jacques-n commented on the pull request:
https://github.com/apache/drill/pull/450#issuecomment-202632855
lgtm
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
GitHub user vkorukanti opened a pull request:
https://github.com/apache/drill/pull/450
DRILL-4549: Add support for more truncation units in date_trunc function
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vkorukanti/drill DRIL
Venki Korukanti created DRILL-4549:
--
Summary: Add support for more units in date_trunc function
Key: DRILL-4549
URL: https://issues.apache.org/jira/browse/DRILL-4549
Project: Apache Drill
Is
Ok, this has nothing to do with multiple files either.
Selecting from a single file produces a schema change. (Who would have
thunk it)
0: jdbc:drill:zk=local> select type, count(*) from
dfs.asa.`/streaming/venuepoint/events/2016-03-28` as s group by type;
Error: UNSUPPORTED_OPERATION ERROR: Hash
Github user laurentgo closed the pull request at:
https://github.com/apache/drill/pull/404
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Github user laurentgo commented on the pull request:
https://github.com/apache/drill/pull/404#issuecomment-202577322
was fixed by @jacques-n in commit edea8b1cf4e5476d803e8b87c79e08e8c3263e04.
I'm closing this PR
---
If your project is set up for it, you can reply to this email and h
GitHub user laurentgo opened a pull request:
https://github.com/apache/drill/pull/449
DRILL-4546: Only generate one zip archive when using apache-release profile
Drill root pom doesn't override completely Apache parent pom configuration
regarding assemblies, which caused a zip ar
Stefán Baxter created DRILL-4548:
Summary: Drill can not select from multiple Avro files
Key: DRILL-4548
URL: https://issues.apache.org/jira/browse/DRILL-4548
Project: Apache Drill
Issue Type
Github user adityakishore commented on the pull request:
https://github.com/apache/drill/pull/443#issuecomment-202576211
I have verified that, with these changes, Drill queries run fine with HBase
0.98 cluster too.
---
If your project is set up for it, you can reply to this email and
Laurent Goujon created DRILL-4547:
-
Summary: Javadoc fails with Java8
Key: DRILL-4547
URL: https://issues.apache.org/jira/browse/DRILL-4547
Project: Apache Drill
Issue Type: Bug
Com
Laurent Goujon created DRILL-4546:
-
Summary: mvn deploy pushes the same zip artifact twice
Key: DRILL-4546
URL: https://issues.apache.org/jira/browse/DRILL-4546
Project: Apache Drill
Issue Ty
Hakim,
Sorry for not responding to you earlier (I just came back from my vacation
in China, unfortunately gmail was blocked there).
As for the cluster sizes and node configurations, I would leave them to the
test suite users to decide.
Thanks,
Dechang
On Wed, Mar 16, 2016 at 10:58 PM, Abdel Haki
GitHub user arina-ielchiieva opened a pull request:
https://github.com/apache/drill/pull/448
DRILL-4544: Improve error messages for REFRESH TABLE METADATA command
1. Added error message when storage plugin or workspace does not exist
2. Updated error message when refresh metadata
Thanks Neeraja for your quick response.
May I know what replaced Hazelcast in that case?
I mean, how does Drill distributed mode currently offer the multicast and
subnet scenarios, or are these scenarios not valid anymore?
Regards,
Pradeeban.
On Mon, Mar 28, 2016 at 3:52 PM, Neeraja Rentachinta
Its not currently used as far as I know.
Drill used this at some point, but we removed it due to issues in
multicast/subnet scenarios in Drill distributed mode.
-Neeraja
On Mon, Mar 28, 2016 at 12:49 PM, Pradeeban Kathiravelu <
kk.pradee...@gmail.com> wrote:
> Hi,
> [1] states that Drill uses Ha
Hi,
[1] states that Drill uses Hazelcast as an embedded distributed cache to
distribute and store metadata and locality information.
However, when I cloned the git repository and looked into the code, it does
not look like Hazelcast is used, except for some unused variable
definitions and pom defi
Great summary. I'll fill in some "non-technical" explanations of some
challenges with Memory as I see. Drill Devs, please keep Paul and I
accurate in our understanding.
First, Memory is already set at the drillbit level... sorta. It's set via
ENV in drill-env, and is not a cluster specific thin
24 matches
Mail list logo
