vel of development and different
requirements (HBASE release version, Kerberos support etc)
_
From: Benjamin Kim <bbuil...@gmail.com<mailto:bbuil...@gmail.com>>
Sent: Saturday, October 8, 2016 11:26 AM
Subject: Re: Spark SQL Thriftserver with HBase
To: Mich Talebzad
M, Mich Talebzadeh <mich.talebza...@gmail.com>
>>>> wrote:
>>>>
>>>> Like any other design what is your presentation layer and end users?
>>>>
>>>> Are they SQL centric users from Tableau background or they may use
>>>> spark
m such loss, damage or destruction.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On 8 October 2016 at 20:15, Benjamin Kim <bbuil...@gmail.com> wrote:
>>>>>>>>>> Mich,
>>>>>>>>>>
>&
tter.
Without naming specifics, there are at least 4 or 5 different implementations
of HBASE sources, each at varying level of development and different
requirements (HBASE release version, Kerberos support etc)
_________
From: Benjamin Kim <bbuil...@gmail.com<mai
>,
"user@spark.apache.org<mailto:user@spark.apache.org>"
<user@spark.apache.org<mailto:user@spark.apache.org>>
Subject: Re: Spark SQL Thriftserver with HBase
Instead of (or additionally to) saving results somewhere, you just start a
thriftserver that expose the Spark t
uthor will in
no case be liable for any monetary damages arising from suchloss, damage or
destruction.
On 8 October 2016 at 19:05, Felix Cheung
<felixcheun...@hotmail.com<mailto:felixcheun...@hotmail.com>> wrote:
Great, then I think those packages as Spark data source should a
ts (HBASE release version, Kerberos support etc)
_________
From: Benjamin Kim <bbuil...@gmail.com<mailto:bbuil...@gmail.com>>
Sent: Saturday, October 8, 2016 11:26 AM
Subject: Re: Spark SQL Thriftserver with HBase
To: Mich Talebzadeh
<mich.talebza...@gmail.com<ma
, by using JDBC everywhere, it simplifies
>>>>>>>> and unifies the code on the JDBC industry standard.
>>>>>>>>
>>>>>>>> Does this make sense?
>>>>>>>>
>>>>>>>>
the same data-center, they will connected to a located database
>>>>>> server using JDBC. Either way, by using JDBC everywhere, it simplifies
>>>>>> and unifies the code on the JDBC industry standard.
>>>>>>
>>>>>> Does this make sense?
>>>>>>
>>>>&
2gBxianrbJd6zP6AcPCCdOABUrV8Pw
>>> <https://www.linkedin.com/profile/view?id=AAEWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>>>
>>>
>>> http://talebzadehmich.wordpress.com
>>>
>>> *Disclaimer:* Use it at your own risk. Any and all responsibility f
ibe the use case.
>
>
>
> HTH
>
>
> Dr Mich Talebzadeh
>
>
>
> LinkedIn *
> https://www.linkedin.com/profile/view?id=AAEWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> <https://www.linkedin.com/profile/view?id=AAEWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>
&
<bbuil...@gmail.com>
Cc: Michael Segel <msegel_had...@hotmail.com>, Jörn Franke
<jornfra...@gmail.com>, Mich Talebzadeh <mich.talebza...@gmail.com>, Felix
Cheung <felixcheun...@hotmail.com>, "user@spark.apache.org"
<user@spark.apache.org>
Subject: Re: Spark SQL
g JDBC.
>>>>> Either way, by using JDBC everywhere, it simplifies and unifies the code
>>>>> on
>>>>> the JDBC industry standard.
>>>>>
>>>>> Does this make sense?
>>>>>
>>>>> Thanks,
>>>
gt;>>
>>>> Like any other design what is your presentation layer and end users?
>>>>
>>>> Are they SQL centric users from Tableau background or they may use
>>>> spark functional programming.
>>>>
>>>> It is best to describe
om
>>>>>> <mailto:mich.talebza...@gmail.com>> wrote:
>>>>>>
>>>>>> Like any other design what is your presentation layer and end users?
>>>>>>
>>>>>> Are they SQL centric users from Tableau back
AWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
>>> <https://www.linkedin.com/profile/view?id=AAEWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>>>
>>>
>>> http://talebzadehmich.wordpress.com
>>>
>>> *Disclaimer:* Use it at your own risk. Any and all responsibility for
__
From: Benjamin Kim <bbuil...@gmail.com<mailto:bbuil...@gmail.com>>
Sent: Saturday, October 8, 2016 11:26 AM
Subject: Re: Spark SQL Thriftserver with HBase
To: Mich Talebzadeh
<mich.talebza...@gmail.com<mailto:mich.talebza...@gmail.com>>
Cc: <us
17 matches
Mail list logo
