impala-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Behm <alex.b...@cloudera.com>
Subject Re: Impala-Kudu - minimal set of dependencies
Date Wed, 26 Apr 2017 15:31:50 GMT
You should be able to bring Impala up without HDFS by passing the
"--abort_on_config_error=false" startup flag.

Just to clarify:
You still need the Hive Metastore with Kudu because table and column
statistics are stored in the Metastore; our plan is to eventually remove
this dependency

On Wed, Apr 26, 2017 at 1:28 AM, Aleksei Maželis <olmazh@gmail.com> wrote:

> Ok, I see. I remember trying to run Impala-Kudu without HDFS, and remember
> that Impala failed to start. But perhaps there is a way to make Impala work
> without HDFS after re-configuring it properly; any hints on which
> configurations to change would be very helpful!
>
> BR,
> Alex
>
> On Tue, Apr 25, 2017 at 7:36 PM, Jim Apple <jbapple@cloudera.com> wrote:
>
>> I believe the Hive Metastore is needed even when Kudu is the storage
>> engine. I don't know if the HDFS namenode and datanodes are needed.
>>
>> On Mon, Apr 24, 2017 at 10:28 PM, Aleksei Maželis <olmazh@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I am looking for the minimal set of dependencies that an Impala-Kudu
>>> setup will have. When reading how-tos and checking available dockerfiles,
>>> the list of items that Impala depends on seems to include at least:
>>> - hadoop-hdfs-namenode
>>> - hadoop-hdfs-datanode
>>> - hive-metastore.
>>>
>>> However, if I understand correctly, when Kudu is used along with Impala,
>>> these aren't necessarily used. So, the question is if the above
>>> dependencies of HDFS and Hive can be avoided, and if so, whether there are
>>> side effects this would bring. And of course, if I am missing some other
>>> mandatory dependencies, hints on those would be more then welcome!
>>>
>>> With best regards,
>>> Alex
>>>
>>
>>
>

Mime
View raw message