others the new value. The workaround is simple: don't change
system options while queries are running.
Thanks,
- Paul
On Wednesday, September 5, 2018, 8:42:02 AM PDT, Joe Auty
j...@thinkdataworks.com> wrote:
Hmmm
So, if user 1 sets the store.format to CSV on Drillbit 1 and wor
that uses it (Query
time of CREATE TABLE as) , the planner reads the value, session first (if
it is different from the system) and then system if the session is not set,
and then completes the query based on the value read.
John
On Wed, Sep 5, 2018 at 10:41 AM, Joe Auty wrote:
Hmmm
So
se session stickiness or pinning on your HA solution and you will be
go. With my DNS round robin it picks a "connecting" drill bit and sticks to
it until the session is done. The settings apply to the drill cluster while
in distributed mode.
On Tue, Sep 4, 2018 at 3:56 PM, Joe Auty wro
the ALTER SYSTEM, you can use ALTER SESSION so it only
applies to the current session, regardless of foreman.
John
On Tue, Sep 4, 2018 at 1:00 PM, Joe Auty wrote:
Hello,
We need to have some queries executed with store.format set to parquet and
some with this option set to CSV. To date we have
Hello,
We need to have some queries executed with store.format set to parquet
and some with this option set to CSV. To date we have experimented with
setting the store format for sessions controlled by using two separate
user logins as a sort of context switch, but I'm wondering if the group
Hello,
We are trying to get this combo working via the instructions found here:
https://stackoverflow.com/questions/32883965/apache-drill-using-google-cloud-storage
We are attempting this with a manually compiled version of 1.14, and can
query GS via gsutil/hadoop commands which suggests the
