drill-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: New to Drill
Date Sun, 26 Oct 2014 06:34:49 GMT
On Fri, Oct 24, 2014 at 10:35 AM, arorav <arorav@uw.edu> wrote:

> 1.       Drill is an incubation project, Is anyone using for production
> applications?
>

Any such production work would be very early.  I don't know for sure of any
such work, but I have heard of several projects that were near production
status.

This should change significantly over the next  quarter or so.

2.       Data repository recommendation:  I have the source data as
> relational and want to perform complex adhoc queries involving joins and
> aggregates. Any recommendation on the data repository for better
> performance.
>

That depends a lot on the sizes of what you are working on.

If you add more details, it would be easier to help, but the basics still
apply.  If broadcast joins are practical, then storing everything in flat
files is probably the best since you will just be scanning the fact table.


>
> 3.       Encrypted Data:  Does drill works against encrypted data? Any
> documentation around it would be helpful?
>

Drill has no specific capabilities to support encryption.  If encryption
means data at rest, drill will not care.  If encryption means that you are
using consistent masking, then Drill may work without ever knowing what the
data is.

At this time, Drill does not encrypt wire transmissions.  If you care
enough to encrypt, you may care about this.  That will change before long.


>
> 4.       Concurrent Queries: As I expect 100s of users running against the
> drill query engine. Is there any limitation on number of queries running
> against drill?
>

There is no specific limit, but there will be practical limits.  I don't
that the boundaries are well tested here yet.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message