Creating SQL skin on Hbase table

[Mich Talebzadeh <mi...@gmail.com>]

Hi,

I have used Phoenix to create SQL views on top of Hbase table and also
created covering engines. The issue I have noticed is that all ingestion
has to go through Phoenix otherwise Phoenix indexes will not be updated.

Another alternative has been to try Hive EXTERNAL tables on top of Hbase
table but only EXTERNAL tables are supported. I was wondering the pros and
cons of using Hive or Phoenix tables on Hbase?

Thanks

Dr Mich Talebzadeh



LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
<https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*



http://talebzadehmich.wordpress.com


*Disclaimer:* Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.

Re: Creating SQL skin on Hbase table

[Josh Elser <el...@apache.org>]

Yes, the expectation is that when using the Phoenix secondary-indexing 
feature, you also must use Phoenix to maintain the accuracy of the 
indices with the data table.

However, even without secondary-indexing, why would you not use Phoenix 
APIs to update? If there are deficiencies in the ability to generate 
data to ingest into Phoenix, that's a problem that should be addressed 
as a new feature/bug in Phoenix. Otherwise, I don't see any reason why 
you wouldn't use Phoenix APIs to read/write data in Phoenix...

Mich Talebzadeh wrote:
> Hi,
>
> I have used Phoenix to create SQL views on top of Hbase table and also
> created covering engines. The issue I have noticed is that all ingestion
> has to go through Phoenix otherwise Phoenix indexes will not be updated.
>
> Another alternative has been to try Hive EXTERNAL tables on top of Hbase
> table but only EXTERNAL tables are supported. I was wondering the pros and
> cons of using Hive or Phoenix tables on Hbase?
>
> Thanks
>
> Dr Mich Talebzadeh
>
>
>
> LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>
>
>
> http://talebzadehmich.wordpress.com
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary damages arising from
> such loss, damage or destruction.
>

Re: Creating SQL skin on Hbase table

[Gunnar Tapper <ta...@gmail.com>]

Have you looked at trafodion.apache.org, which uses HBase as its native
storage engine?

On Sun, Dec 25, 2016 at 4:28 AM, Chetan Khatri <ch...@gmail.com>
wrote:

> If I would like to read Incremental data from HBase , How Phoenix can help
> me ?
>
> On Fri, Dec 23, 2016 at 2:20 AM, Mich Talebzadeh <
> mich.talebzadeh@gmail.com>
> wrote:
>
> > Hi,
> >
> > I have used Phoenix to create SQL views on top of Hbase table and also
> > created covering engines. The issue I have noticed is that all ingestion
> > has to go through Phoenix otherwise Phoenix indexes will not be updated.
> >
> > Another alternative has been to try Hive EXTERNAL tables on top of Hbase
> > table but only EXTERNAL tables are supported. I was wondering the pros
> and
> > cons of using Hive or Phoenix tables on Hbase?
> >
> > Thanks
> >
> > Dr Mich Talebzadeh
> >
> >
> >
> > LinkedIn * https://www.linkedin.com/profile/view?id=
> > AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> > <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCd
> > OABUrV8Pw>*
> >
> >
> >
> > http://talebzadehmich.wordpress.com
> >
> >
> > *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> > loss, damage or destruction of data or any other property which may arise
> > from relying on this email's technical content is explicitly disclaimed.
> > The author will in no case be liable for any monetary damages arising
> from
> > such loss, damage or destruction.
> >
>



-- 
Thanks,

Gunnar
*If you think you can you can, if you think you can't you're right.*

Re: Creating SQL skin on Hbase table

[Chetan Khatri <ch...@gmail.com>]

If I would like to read Incremental data from HBase , How Phoenix can help
me ?

On Fri, Dec 23, 2016 at 2:20 AM, Mich Talebzadeh <mi...@gmail.com>
wrote:

> Hi,
>
> I have used Phoenix to create SQL views on top of Hbase table and also
> created covering engines. The issue I have noticed is that all ingestion
> has to go through Phoenix otherwise Phoenix indexes will not be updated.
>
> Another alternative has been to try Hive EXTERNAL tables on top of Hbase
> table but only EXTERNAL tables are supported. I was wondering the pros and
> cons of using Hive or Phoenix tables on Hbase?
>
> Thanks
>
> Dr Mich Talebzadeh
>
>
>
> LinkedIn * https://www.linkedin.com/profile/view?id=
> AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCd
> OABUrV8Pw>*
>
>
>
> http://talebzadehmich.wordpress.com
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary damages arising from
> such loss, damage or destruction.
>