I think we should get rid of repeated_contains, and instead have a set of
boolean functions that operate on repeated types. For every boolean
function, there would be 2 corresponding boolean functions which operate on
repeated types.
the "any" version would return true if the corresponding
These are cool.
Want me to put them in https://github.com/mapr-demos/simple-drill-functions
while the discussion about how/whether/where to put them in Drill happens?
I can add you as a collaborator as well.
On Thu, Oct 1, 2015 at 2:02 PM, Stefán Baxter
wrote:
>
Should you be able to access an HBase table for which there is Hive metadata?
That provide an alternative to the Convert functions required to access HBase
without metadata. I opened a Jira to report this but it hasn't been acted on.
https://issues.apache.org/jira/browse/DRILL-3739
Hey all, curious if there is a tentative release date for 1.2.
Thanks,
John
In Drill, a file is a table, but so is a directory.
So go ahead and do CTAS on each day's data, putting each new file into a
directory, possibly partitioned by month. Then query based on the directory
or super-directory.
On Mon, Oct 5, 2015 at 5:20 PM, John Omernik wrote:
>
Release process has started on the dev list already.
Depending on how many candidates there are, it shouldn't be long.
On Mon, Oct 5, 2015 at 5:03 PM, John Omernik wrote:
> Hey all, curious if there is a tentative release date for 1.2.
>
> Thanks,
>
> John
>
Hi,
I'm executing simple statement in current master branch of drill. Getting
following exceptions:
java.sql.SQLException: Unexpected RuntimeException:
java.lang.IndexOutOfBoundsException: Index: 0
at
org.apache.drill.jdbc.impl.DrillCursor.nextRowInternally(DrillCursor.java:261)
at
Nope, Same query works fine on sqlline and in v1.1.0 release too. The
issue is V1.1.0 doesn't support prepared statement so I thought if
current build is supporting it, I will use it. But I'm encountering
whole new issues here.
On Monday 05 October 2015 09:17 PM, Abdel Hakim Deneche wrote:
Hey I've seen this issue when using an incompatible JDBC jar - for example,
using 1.2 jar and a 1.1 Drill-bit. This was with a JDBC program. Can you
make sure you are using the same version of JDBC JAR shipped with the Drill?
On Mon, Oct 5, 2015 at 8:55 AM, Nikunj Thakkar