kkhatua edited a comment on issue #1279: DRILL-5735: Allow search/sort in the
Options webUI
URL: https://github.com/apache/drill/pull/1279#issuecomment-413764952
@arina-ielchiieva please review.
This contains changes as requested.
The UI and the System tables, both function as
kkhatua commented on issue #1279: DRILL-5735: Allow search/sort in the Options
webUI
URL: https://github.com/apache/drill/pull/1279#issuecomment-413764952
@arina-ielchiieva please review.
This is an automated message from
diegocaro opened a new pull request #1435: Parquet compression is disabled by
default
URL: https://github.com/apache/drill/pull/1435
Compression on parquet files are disabled by default, check line 577 on
drill-module.conf ->
sohami closed pull request #1434: DRILL-6694: NPE in UnnestRecordBatch when
query uses a column name no…
URL: https://github.com/apache/drill/pull/1434
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of
Krystal created DRILL-6695:
--
Summary: Graceful shutdown removes spill directory before query
finished
Key: DRILL-6695
URL: https://issues.apache.org/jira/browse/DRILL-6695
Project: Apache Drill
sohami commented on a change in pull request #1434: DRILL-6694: NPE in
UnnestRecordBatch when query uses a column name no…
URL: https://github.com/apache/drill/pull/1434#discussion_r210759060
##
File path:
sohami opened a new pull request #1434: DRILL-6694: NPE in UnnestRecordBatch
when query uses a column name no…
URL: https://github.com/apache/drill/pull/1434
…t present in data
This is an automated message from the Apache
Sorabh Hamirwasia created DRILL-6694:
Summary: NPE in UnnestRecordBatch when query uses a column name
not present in data
Key: DRILL-6694
URL: https://issues.apache.org/jira/browse/DRILL-6694
ilooner commented on issue #1344: DRILL-6461: Added basic data correctness
tests for hash agg, and improved operator unit testing framework.
URL: https://github.com/apache/drill/pull/1344#issuecomment-413667931
@sohami The PR is ready for another round of review.
I removed the fix
Anton Gozhiy created DRILL-6693:
---
Summary: When a query is started from Drill Web Console, the UI
becomes inaccessible until the query is completed
Key: DRILL-6693
URL:
Hi Mehran,
This is a question for user mailing list.
Looks like there are no issues with it, you can run Drill in distributed
mode on Windows, Linux or MacOS based machines.
It necessary to specify *zk.connect* for Zookeeper hostname and port number
in *drill-override.conf* file and to run
Vitalii Diravka created DRILL-6692:
--
Summary: Undeclared dependencies for Nullable and NotNull
annotations
Key: DRILL-6692
URL: https://issues.apache.org/jira/browse/DRILL-6692
Project: Apache Drill
Hi,
I wanted to know if it is possible or possible by minimal effort to have
distributed drills that work on local file system of their own?
We do not want to have HDFS as file system?
Thank you in advance.
Best Regards,
[LOGO1]
Mehran Dashti
Product Leader
09125902452
Thanks for the background Jinfeng, your explanation brings us back to the topic
Arina raised: the state and direction of the Drill project.
For several years now, Drill has said, essentially, "dabble with raw data all
you like early in the project, but for production, ETL your data into
Volodymyr Vysotskyi created DRILL-6691:
--
Summary: Unify checkstyle-config.xml files
Key: DRILL-6691
URL: https://issues.apache.org/jira/browse/DRILL-6691
Project: Apache Drill
Issue
arina-ielchiieva commented on issue #1419: DRILL-6662: Access AWS access key ID
and secret access key using Cred…
URL: https://github.com/apache/drill/pull/1419#issuecomment-413512174
+1, LGTM.
This is an automated message
KazydubB commented on issue #1419: DRILL-6662: Access AWS access key ID and
secret access key using Cred…
URL: https://github.com/apache/drill/pull/1419#issuecomment-413512145
@arina-ielchiieva I have addressed review comments. Could you take a look,
please?
arina-ielchiieva commented on a change in pull request #1419: DRILL-6662:
Access AWS access key ID and secret access key using Cred…
URL: https://github.com/apache/drill/pull/1419#discussion_r210559817
##
File path:
KazydubB commented on a change in pull request #1419: DRILL-6662: Access AWS
access key ID and secret access key using Cred…
URL: https://github.com/apache/drill/pull/1419#discussion_r210559211
##
File path:
arina-ielchiieva commented on a change in pull request #1419: DRILL-6662:
Access AWS access key ID and secret access key using Cred…
URL: https://github.com/apache/drill/pull/1419#discussion_r210540931
##
File path: distribution/src/resources/core-site-example.xml
##
@@
arina-ielchiieva commented on a change in pull request #1419: DRILL-6662:
Access AWS access key ID and secret access key using Cred…
URL: https://github.com/apache/drill/pull/1419#discussion_r210541907
##
File path:
Hello,
After discussing this topic with Alex, this is what we are trying to do.
We are using MapR, with different tenants for different functional teams,
each of these being represented by a dedicated LDAP group.
We are planning to deploy Drill on Yarn, so that each group can deploy its
own drill
I think there's no schema-free data. To one ad-hoc query, one file, its
schema is already defined. The schema is just discovered by the Drill not
defined the user explicitly now.
On Thu, Aug 16, 2018 at 2:29 PM Jinfeng Ni wrote:
> btw: In one project that I'm currently working (an application
btw: In one project that I'm currently working (an application related to
IOT), I'm leveraging Drill's schema-on-read ability, without requiring user
to predefine table DDL.
On Wed, Aug 15, 2018 at 11:15 PM, Jinfeng Ni wrote:
> The use case Weijie described seems to fall into the category of
The use case Weijie described seems to fall into the category of
traditional data warehouse, i.e, schemas are predefined by users, data
strictly conforms to schema. Certainly this is one important uses, and I
agreed that the schema-on-read logic in Drill run-time indeed is a
disadvantage for such
25 matches
Mail list logo
