I’d like to complete DRILL-6104 and get that in.
—C
> On Jun 12, 2018, at 20:16, Boaz Ben-Zvi wrote:
>
> Hello Drillers,
> Nearly three months have passed since the 1.13.0 release, and it is time to
> start planning for the 1.14.0 ; I volunteer to manage the new release.
> If there is any
Some of us are trying to finish DRILL-5999 (and related subtasks) in time
for 1.14. We have a couple of weeks' worth of work left (or so we think).
Can you keep this on your list of items to track and we can make a call as
we get closer to the release date.
On Tue, Jun 12, 2018 at 5:16 PM, Boaz
Looks like Boaz just started a conversation on the next release. For the
record, we try to do the release every three months but if any committer
feels the need to do an earlier release, we can certainly do so (provided
everyone agrees).
On Tue, Jun 12, 2018 at 1:43 PM, Charles Givre wrote:
> Hi
[
https://issues.apache.org/jira/browse/DRILL-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pritesh Maker resolved DRILL-6008.
--
Resolution: Fixed
> Unable to shutdown Drillbit using short domain name
> -
[
https://issues.apache.org/jira/browse/DRILL-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pritesh Maker resolved DRILL-6039.
--
Resolution: Fixed
> drillbit.sh graceful_stop does not wait for fragments to complete before
>
Hello Drillers,
Nearly three months have passed since the 1.13.0 release, and it is time to
start planning for the 1.14.0 ; I volunteer to manage the new release.
If there is any ongoing work not yet committed into the Apache Drill master,
that you strongly feel MUST be included in the 1.14 r
We are targeting the next Apache Drill release by the end of this month. Boaz
has volunteered to drive the 1.14 release and will send out a separate email
about it.
Pritesh
On 6/12/18, 1:44 PM, "Charles Givre" wrote:
Hi Parth,
When is the next release of Drill going to be?
— C
Hi Parth,
When is the next release of Drill going to be?
— C
> On Jun 12, 2018, at 16:42, Parth Chandra wrote:
>
> Short summary of the call -
>
> Attendees:
> Abhishek, Aman, Arina, Oleksander, Gautam, Samiksha, Timothy, Vitalii, Parth,
> DC, Sorabh, Jyothsna, Chun, Robert, Hau, Boaz, Prites
Short summary of the call -
Attendees:
Abhishek, Aman, Arina, Oleksander, Gautam, Samiksha, Timothy, Vitalii, Parth,
DC, Sorabh, Jyothsna, Chun, Robert, Hau, Boaz, Pritesh, Kunal
Arina - case insensitive storage plugin and workspace names
General agreement on case insenstive names. Let us im
Paul, I think this proposal was specific to storage plugin and workspace
*names*. And not for the whole of Drill.
I agree it makes sense to have these names case insensitive, to improve
user experience. The only impact to current users I can think of is if
someone created two storage plugins dfs a
Hi All,
As it turns out, this topic has been discussed, in depth, previously. Can't
recall if it was on this list, or in a JIRA.
We face a number of constraints:
* As was noted, for some data sources, the data source itself has case
insensitive names. (Windows file systems, RDBMSs, etc.)
* In
Yes, that seems ok to me...since the plugin name and workspace are logical
entities and don't correspond to a path.
There could be compatibility issues if certain users have relied on the
case-sensitive names, but those would be temporary.
Aman
On Tue, Jun 12, 2018 at 8:35 AM, Arina Yelchiyeva <
Bohdan Kazydub created DRILL-6491:
-
Summary: Prevent merge join for full outer join at planning stage
Key: DRILL-6491
URL: https://issues.apache.org/jira/browse/DRILL-6491
Project: Apache Drill
To make it clear we have three notions here: storage plugin name, workspace
(schema) and table name (dfs.root.`/tmp/t`).
My suggestion is the following:
Storage plugin names to be case insensitive (DFS vs dfs, INFORMATION_SCHEMA
vs information_schema).
Workspace (schemas) names to be case insensit
Drill is dependent on the underlying file system's case sensitivity. On
HDFS one can create 'hadoop fs -mkdir /tmp/TPCH' and /tmp/tpch which are
separate directories.
These could be set as workspace in Drill's storage plugin configuration and
we would want the ability to query both. If we chan
Vlad Rozov created DRILL-6490:
-
Summary: Fix tests that rely on wrong statistics and were disabled
after parquet library upgrade
Key: DRILL-6490
URL: https://issues.apache.org/jira/browse/DRILL-6490
Proje
Arina Ielchiieva created DRILL-6489:
---
Summary: Fix filter push down for Hbase & Mapr-DB binary tables
when convert function is used in a view
Key: DRILL-6489
URL: https://issues.apache.org/jira/browse/DRILL-6489
I'd like to discuss case insensitive storage plugin and workspaces names
(sent the email to the dev & user mailing lists with the details).
Kind regards,
Arina
On Tue, Jun 12, 2018 at 4:07 AM Timothy Farkas wrote:
> Hi,
>
> I'd like to give the presentation for the resource management proposal.
Hi all,
Currently Drill we treat storage plugin names and workspaces as
case-sensitive [1].
Names for storage plugins and workspaces are defined by the user. So we
allow to create plugin -> DFS and dfs, workspace -> tmp and TMP.
I have a suggestion to move to case insensitive approach and won't al
19 matches
Mail list logo