phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kanagha <er.kana...@gmail.com>
Subject Re: phoenix spark options not supporint query in dbtable
Date Thu, 17 Aug 2017 07:07:40 GMT
Also, I'm using phoenixTableAsDataFrame API to read from a pre-split
phoenix table. How can we ensure read is parallelized across all executors?
Would salting/pre-splitting tables help in providing parallelism?
Appreciate any inputs.

Thanks


Kanagha

On Wed, Aug 16, 2017 at 10:16 PM, kanagha <er.kanagha@gmail.com> wrote:

> Hi Josh,
>
> Per your previous post, it is mentioned "The phoenix-spark parallelism is
> based on the splits provided by the Phoenix query planner, and has no
> requirements on specifying partition columns or upper/lower bounds."
>
> Does it depend upon the region splits on the input table for parallelism?
> Could you please provide more details?
>
>
> Thanks
>
>
>
> --
> View this message in context: http://apache-phoenix-user-
> list.1124778.n5.nabble.com/phoenix-spark-options-not-
> supporint-query-in-dbtable-tp1915p3810.html
> Sent from the Apache Phoenix User List mailing list archive at Nabble.com.
>

Mime
View raw message