Thanks For your response Kunal.
I tried in both the way but the outcome is same the window where I submitted
the query is loading and other one is getting stuck. But the same query is
working well with 1.12 version in which I could monitor the query status and
submit another query.
I am
A. +1.
B. Every byte in a binary data may require up to 4 bytes (0xXX) in the
string representation, so 80 may work, 60 should reliably work.
Thank you,
Vlad
On 7/17/18 13:14, John Omernik wrote:
Yet this works?
string_binary(byte_substr(`data`, 1, 80))
On Tue, Jul 17, 2018 at 3:12
Yet this works?
string_binary(byte_substr(`data`, 1, 80))
On Tue, Jul 17, 2018 at 3:12 PM, John Omernik wrote:
> So on B. I found the BYTE_SUBSTR and only send 200 bytes to the
> string_binary function, I still get an error. Something else is happening
> here...
>
> select `type`,
So on B. I found the BYTE_SUBSTR and only send 200 bytes to the
string_binary function, I still get an error. Something else is happening
here...
select `type`, `timestamp`, `src_ip`, `dst_ip`, `src_port`, `dst_port`,
string_binary(byte_substr(`data`, 1, 200)) as mydata from
You could try the reverse. Monitor in the initial window, while submitting the
query in another window.
That said, the reason your console is getting stuck is by design. The browser
tab from which you submit the query is the window where you'll receive the
results of the query. Hence, the
Thanks Vlad a couple of thoughts.
A. I think that should be fixed. That seems like a limitation that is both
unexpected and undocumented.
B. Is there a way, if my data in the table is returned as binary to start
with, for me to return the first 256 bytes? I tried substring, and tries to
force
In case of DRILL-6607 the issue lies in the implementation of
"string_binary" function: it is not prepared to handle incoming data
that when converted to a binary string would exceed 256 bytes as it does
not reallocate the output buffer. Until the function code is fixed, the
only way to avoid
Hey guys,
Adding this JVM flag to the drill-env.sh file made it to work.
export JAVA_TOOL_OPTIONS="-Dfile.encoding=UTF8"
Thank you very much.
On Tue, Jul 17, 2018 at 1:49 AM, Kunal Khatua wrote:
> Hi Carlos
>
> It looks similar to an issue reported previously:
>
Hi Team,
I am using Drill 1.13.0 version. I am facing below issues which were not there
in 1.12.0
1. When I am submitting query I am not able to open Drill web-console in
another window to monitor the currently running query status.
2. Not able to submit another query once a
