Hello JJ,
No, currently Impala uses one thread to execute the join (without
regard for the amount of partitions that fit into memory).
HTH
On 25 October 2017 at 05:44, 俊杰陈 wrote:
> Hi
>
> When Impala does a partitioned join on a node, it split the build input
> into
+1
On 18 October 2017 at 03:40, Tim Armstrong wrote:
> +1
>
> On 17 Oct. 2017 8:38 pm, "Alexander Behm" wrote:
>
>> +1
>>
>> On Tue, Oct 17, 2017 at 8:18 PM, Taras Bobrovytsky
>> wrote:
>>
>> > +1
>> >
>> > On Tue, Oct 17,
wrote:
> I try to use ' invalidate metadata' for the whole catalog, But the modified
> table is still empty. I am doubt the only way is restart catalogd.
>
> BTW, I test with the newest version(2.10.0)
>
> 2017-10-13 0:17 GMT+08:00 Jeszy <jes...@gmail.com>:
>
>> T
;
>
>
> At 2017-10-13 00:30:12, "Jeszy" <jes...@gmail.com> wrote:
>>See the docs on LOAD DATA:
>>http://impala.apache.org/docs/build/html/topics/impala_load_data.html
>>
>>"In the interest of speed, only limited error checking is done. If the
>&
See the docs on LOAD DATA:
http://impala.apache.org/docs/build/html/topics/impala_load_data.html
"In the interest of speed, only limited error checking is done. If the
loaded files have the wrong file format, different columns than the
destination table, or other kind of mismatch, Impala does not
This does sound like a bug. What version are you using? Do you see any
errors in the catalog logs?
I think a global invalidate metadata should work, and it's a bit less
intrusive than a catalog restart. In general, it is a good idea to do
all metadata operations from Impala if you are using Impala
Hello Quanlong,
This is https://issues.apache.org/jira/browse/IMPALA-6009, there's
already a fix (but see follow up talk on jira).
HTH
On 4 October 2017 at 01:53, 黄权隆 wrote:
> Hi all,
>
> I encountered a compile error when I try to recompile impala yesterday. The
>
g/faq.html
FWIW, you can use Hive's open source driver to connect to impala, but
since it's not as widely used as Cloudera's drivers you may run into a
few issues.
On 19 September 2017 at 10:55, sky <x_h...@163.com> wrote:
> Thank you Jeszy.
> But doesn't impala provide an open-s
If you are referring to Cloudera's JDBC and ODBC connectors,
unfortunately those are proprietary.
On 18 September 2017 at 11:55, sky wrote:
> Hi all,
> Could you give me a impala driver source code connection?
3 15:02 GMT+08:00 孙清孟 <sqm2...@gmail.com>:
>
>> Hi Jeszy:
>> Thanks for your reply.
>>
>> On another cluster with two instances, I do the same SQL, and the file
>> size is smaller :
>>
>> F00:PLAN FRAGMENT [RANDOM] hosts=2 instances=2
>> WRITE TO
Putting some more files in the source table will allow you to use more hosts.
On 3 August 2017 at 05:08, Taras Bobrovytsky wrote:
> Yes, it looks like all the work is being done on a single node because
> hosts=1.
>
> On Wed, Aug 2, 2017 at 7:55 PM, 孙清孟
Hey,
No problems usually, but now It's down for me as well. According to
status.apache.org, the service seems to be struggling.
On 24 July 2017 at 18:15, Matthew Jacobs wrote:
> Hey,
>
> I've been noticing a lot of slowness/timeouts on the Apache JIRA. Has
> anyone else
With CM you can just add Impala as a new service to your cluster. Use
the dropdown next to the cluster name. A binary version of impala is
shipped as part of the CDH 5.11 parcels that you have installed.
On 21 June 2017 at 11:58, 孙清孟 wrote:
> Hi Tim,
> I've built Impala
Hey,
It looks like all the time is spent waiting for the client to fetch the results:
- ClientFetchWaitTimer: 17m31s
Try doing:
impala-shell -B -q ''
HTH
2017-04-28 14:51 GMT+02:00 吴朱华 :
> Maybe I just paste some main thing on mail , and congratulation on IPO
> thing.
>
Hey,
that's not possible from within impala. If you go directly to the
HMS's backing DB, you can query that.
What information are you looking for?
Thanks.
On Thu, Apr 6, 2017 at 3:02 PM, 吴朱华 wrote:
> Hi guys:
>
> Currently, we are using "show databases","show tables" or
15 matches
Mail list logo