[jira] [Resolved] (DRILL-3802) Throw unsupported error for ROLLUP/GROUPING

[ https://issues.apache.org/jira/browse/DRILL-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-3802. --- Resolution: Fixed Fix Version/s: 1.3.0 Fixed in commit: 19b4b798b6756c6a140a05c2ca8e6e79778b1df

[GitHub] drill pull request: DRILL-3802: Throw unsupported error for Rollup...

Github user asfgit closed the pull request at: https://github.com/apache/drill/pull/209 --- 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

[GitHub] drill pull request: DRILL-3340: Add operator metrics registry for ...

Github user sudheeshkatkam commented on the pull request: https://github.com/apache/drill/pull/216#issuecomment-150099503 I am not a UI expert; where is the best place to present operator metrics as a table in our query profile page? --- If your project is set up for it, you can repl

[GitHub] drill pull request: DRILL-3340: Add operator metrics registry for ...

GitHub user sudheeshkatkam opened a pull request: https://github.com/apache/drill/pull/216 DRILL-3340: Add operator metrics registry for metric definitions + Display metrics as a table within an operator profile panel + Rename FragmentStats#getOperatorStats to newOperatorStats Y

Re: [DISCUSS] Design Documents

I've been quietly lurking on this thread as a n00b to the Drill community :). I like the approach that's been proposed, and agree that setting an example for others to follow will be a great motivating factor for others to follow suit. On the MapR end, I'll work with the team to "encourage" more

[jira] [Created] (DRILL-3964) CTAS fails with NPE when source JSON file is empty

Abhishek Girish created DRILL-3964: -- Summary: CTAS fails with NPE when source JSON file is empty Key: DRILL-3964 URL: https://issues.apache.org/jira/browse/DRILL-3964 Project: Apache Drill I

Re: Help with Hadoop upgrade

I documented the failure on the JIRA. I don’t think there is more information as no exception was thrown. > On Oct 21, 2015, at 5:30 PM, Abdel Hakim Deneche > wrote: > > what kind of failures are you seeing ? > > On Wed, Oct 21, 2015 at 4:09 PM, andrew wrote: > >> hey drillers - >> >> i’ve

Re: Help with Hadoop upgrade

what kind of failures are you seeing ? On Wed, Oct 21, 2015 at 4:09 PM, andrew wrote: > hey drillers - > > i’ve been blocked trying to get our hadoop dependency upgraded to 2.7.1 ( > https://issues.apache.org/jira/browse/DRILL-3749 < > https://issues.apache.org/jira/browse/DRILL-3749>). having t

[GitHub] drill pull request: DRILL-3739: Fix issues in reading Hive tables ...

GitHub user vkorukanti opened a pull request: https://github.com/apache/drill/pull/215 DRILL-3739: Fix issues in reading Hive tables with StorageHandler configuration (eg. Hive-HBase tables) Issue is for Hive tables with custom storage handlers (such as HBase backed Hive tables), I

Re: Partial aggregation in Drill-on-Phoenix

Changes look great, Maryann. Would you mind pulling those in, Jacques? Thanks, James On Mon, Oct 19, 2015 at 11:50 AM, Maryann Xue wrote: > Made another two check-ins to https://github.com/jacques-n/drill/pull/5, > first one for the changes James had suggested. The second check-in included > so

Re: select from table with options

TL;DR: I agree that there is some overlap, but I meant to say that "Select with Option" is needed even if we have a .drill feature. I'm assuming the .drill file has to be collocated with the data being analyzed. For example in HDFS, if I have /logs/foo/2015/10/21/my.log i add a .drill file in /lo

Re: select from table with options

can you elaborate on what you mean by .drill is a different use case. In my mind, .drill has 2 use cases - a way to specify hints to Drill on how read certain datasets (and potentially optimize the queries on the datasets) and a way to save the definitions of objects created via Drill for reuse/a

[GitHub] drill pull request: DRILL-3484: Error with no-argument functions w...

Github user jaltekruse closed the pull request at: https://github.com/apache/drill/pull/85 --- 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

Re: select from table with options

I think of .drill files as a different use case but there is potentially some overlap. Some things to keep in mind: - The person analyzing the data has often read-only access. - having to write a config file on one end of the system and then query on the other end is not analyst friendly We shou

Help with Hadoop upgrade

hey drillers - i’ve been blocked trying to get our hadoop dependency upgraded to 2.7.1 (https://issues.apache.org/jira/browse/DRILL-3749 ). having trouble with TestDrillbitResilience.cancelAfterEverythingIsCompleted(). the test runs fine on my

Re: select from table with options

Another alternative to do this to specify a metadata file (.drill files) that came up in some of the earlier discussions to solve similar use cases. Rather than centrally defining configurations in storage plugin (which is what Drill does today), .drill files allow more granularity , potentially at

Re: select from table with options

I like the approach of using views to add missing metadata to an existing raw dataset. The raw datasets stay the same and the view becomes the interface to the data. Nothing is mutated and we know how things are derived from one another. TLDR: I'm trying to summarize the options bellow and add a f

[DISCUSS] Processing non-printable characters in Drill

Hi All, This discussion is related to DRILL-2322. It looks like Drill processes non-printable characters in both cases, with and without the new text reader (exec.storage.enable_new_text_reader) Should we throw an error since these are non-printable characters ? for more details please take a loo

[jira] [Created] (DRILL-3963) Read raw key values from sequence files

amit hadke created DRILL-3963: - Summary: Read raw key values from sequence files Key: DRILL-3963 URL: https://issues.apache.org/jira/browse/DRILL-3963 Project: Apache Drill Issue Type: Bug

[GitHub] drill pull request: Add Sequence file support.

Github user jinfengni commented on the pull request: https://github.com/apache/drill/pull/214#issuecomment-150038654 Is there a public JIRA created for PR? --- 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

[GitHub] drill pull request: Add Sequence file support.

Github user StevenMPhillips commented on a diff in the pull request: https://github.com/apache/drill/pull/214#discussion_r42687575 --- Diff: protocol/src/main/java/org/apache/drill/exec/proto/beans/CoreOperatorType.java --- @@ -58,7 +58,8 @@ HBASE_SUB_SCAN(33), W

[GitHub] drill pull request: Add Sequence file support.

Github user jaltekruse commented on a diff in the pull request: https://github.com/apache/drill/pull/214#discussion_r42684543 --- Diff: protocol/src/main/java/org/apache/drill/exec/proto/beans/CoreOperatorType.java --- @@ -58,7 +58,8 @@ HBASE_SUB_SCAN(33), WINDOW

[GitHub] drill pull request: Add Sequence file support.

Github user amithadke commented on a diff in the pull request: https://github.com/apache/drill/pull/214#discussion_r42682512 --- Diff: protocol/src/main/java/org/apache/drill/exec/proto/beans/CoreOperatorType.java --- @@ -58,7 +58,8 @@ HBASE_SUB_SCAN(33), WINDOW(

[GitHub] drill pull request: Add Sequence file support.

Github user jaltekruse commented on a diff in the pull request: https://github.com/apache/drill/pull/214#discussion_r42682341 --- Diff: protocol/src/main/java/org/apache/drill/exec/proto/beans/CoreOperatorType.java --- @@ -58,7 +58,8 @@ HBASE_SUB_SCAN(33), WINDOW

[GitHub] drill pull request: Add Sequence file support.

Github user amithadke commented on the pull request: https://github.com/apache/drill/pull/214#issuecomment-150022336 @jaltekruse @StevenMPhillips @jacques-n --- 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

[GitHub] drill pull request: Add Sequence file support.

GitHub user amithadke opened a pull request: https://github.com/apache/drill/pull/214 Add Sequence file support. Read key values from sequence file as VarBinary. You can merge this pull request into a Git repository by running: $ git pull https://github.com/amithadke/drill loc

[jira] [Created] (DRILL-3962) Add support of ROLLUP, CUBE, GROUPING_SETS, GROUPING, GROUPING_ID, GROUP_ID support

Jinfeng Ni created DRILL-3962: - Summary: Add support of ROLLUP, CUBE, GROUPING_SETS, GROUPING, GROUPING_ID, GROUP_ID support Key: DRILL-3962 URL: https://issues.apache.org/jira/browse/DRILL-3962 Project:

[GitHub] drill pull request: DRILL-3802: Throw unsupported error for Rollup...

Github user jinfengni commented on a diff in the pull request: https://github.com/apache/drill/pull/209#discussion_r42679515 --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/planner/sql/parser/UnsupportedOperatorsVisitor.java --- @@ -305,6 +313,105 @@ public SqlNode vi

Re: HBase get.setTimeRange() support

I would think if we want to expose the timestamp field, we should add another layer of nesting. In other words, every qualifier, which is currently a single value, would actually be a map, which includes a value field and timestamp field. Of course, we could also take it a step further and expose v

[GitHub] drill pull request: DRILL-2967: Incompatible types error reported ...

Github user adeneche commented on the pull request: https://github.com/apache/drill/pull/213#issuecomment-14031 @mehant can you please review ? thx --- 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

[GitHub] drill pull request: DRILL-2967: Incompatible types error reported ...

GitHub user adeneche opened a pull request: https://github.com/apache/drill/pull/213 DRILL-2967: Incompatible types error reported in a "not in" query wit… …h compatible data types You can merge this pull request into a Git repository by running: $ git pull https://github.c

Re: HBase get.setTimeRange() support

We've talked about how to expose this but haven't yet exposed it. What do you think a good way to expose this would be? A separate set of columns (e.g. qualifier and qualifier_timestamp)? Do you also need access to multiple versions or only the timestamp? -- Jacques Nadeau CTO and Co-Founder, Drem

Re: select from table with options

Whatever API is used to scan files from SQL, there will need to be a corresponding way to accomplish the same thing in a user interface. Probably a form with various fields, some of them with drop-boxes etc. And ideally a facility that samples a few hundred rows to deduce the probable field names

Re: select from table with options

> This fourth is also least extensible and thus most disenfranchising for > those outside the inner group. > > Table functions (hopefully) would be something that others could implement. This is a brainstorm about a user apis... It isn't appropriate to shoot down ideas immediately in a brainstorm

Re: select from table with options

My initial inclination of a table function was that it sounds kind of sketchy. But given Julian's elaboration and description this sounds like a great idea. >From a user perspective this is easy to understand and flexible. To me I see this table function model effectively like a hint for how to ha