Thanks Tim.
I understand java frontend seems to be major hurdle. If any thread is going
on for the same would certainly like to be part of it.

We are working with apache geode and seeking support for the same.

Thanks,
Deepak

On Wed, Nov 30, 2016 at 10:38 AM, Tim Armstrong <tarmstr...@cloudera.com>
wrote:

>
>
> On Tue, Nov 29, 2016 at 2:34 PM, Tim Armstrong <tarmstr...@cloudera.com>
> wrote:
>
>> Hi Deepak,
>>   We don't support Hive's storage handler API - we have our own HBase
>> support that was use for HBase tables. We also have similar support for
>> Kudu tables. To add equivalent support system you'd need to add frontend
>> Java support for planning queries against that table type and backend C++
>> support for scanning the data. This kind of thing would be a pretty big
>> change so there would need to be buy-in from the community.
>>
>> We also have a Java data source API that lets you write a Java class that
>> scans an arbitrary data source. That is easier to use but has limitations
>> (only executes on a single node, performance is worse than other table
>> types. E.g. see this thread: https://groups.google.com/a/cl
>> oudera.org/forum/#!topic/impala-user/egcflD8XkHc
>>
>> What key-value store are you working with, out of curiousity?
>>
>> - Tim
>>
>> On Tue, Nov 29, 2016 at 8:41 AM, Deepak Dixit <deepakdixit2...@gmail.com>
>> wrote:
>>
>>> Hello Impala Team,
>>>
>>> I am working on building application which stores data in in memory key
>>> value store and would like to query though impala.
>>> I have found that Impala works well with Hbase with the
>>> HBaseStoreageHandler which is essentially connector for Hive.
>>> I have written similar connector for our key value store. And hive works
>>> well with that. But when I tries to run select query on table created
>>> through hive it gives me following error
>>>
>>> AnalysisException: Failed to load metadata for table: 'table_1'
>>> CAUSED BY: TableLoadingException: Unrecognized table type for table:
>>> default.table_1
>>>
>>> Can you please help in understanding the issue and possible resolution?
>>>
>>> Thank You
>>>
>>> --
>>> From:
>>>
>>> Deepak D Dixit
>>> deepakdixit2...@gmail.com
>>> +919028507537
>>>
>>
>>
>


-- 
From:

Deepak D Dixit
deepakdixit2...@gmail.com
+919028507537

Reply via email to