[ 
https://issues.apache.org/jira/browse/PHOENIX-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761853#comment-15761853
 ] 

Hudson commented on PHOENIX-3532:
---------------------------------

SUCCESS: Integrated in Jenkins build Phoenix-master #1516 (See 
[https://builds.apache.org/job/Phoenix-master/1516/])
PHOENIX-3532 Pass tenantId parameter to PhoenixRDD when reading (Nico 
(jmahonin: rev e45b5a706107e31bc6e5b8289725db097b2820eb)
* (edit) 
phoenix-spark/src/main/scala/org/apache/phoenix/spark/SparkContextFunctions.scala
* (edit) 
phoenix-spark/src/it/scala/org/apache/phoenix/spark/PhoenixSparkITTenantSpecific.scala
* (edit) phoenix-spark/src/it/resources/tenantSetup.sql
* (edit) phoenix-spark/src/main/scala/org/apache/phoenix/spark/PhoenixRDD.scala
* (edit) 
phoenix-spark/src/it/scala/org/apache/phoenix/spark/AbstractPhoenixSparkIT.scala
* (edit) 
phoenix-spark/src/main/scala/org/apache/phoenix/spark/SparkSqlContextFunctions.scala


> Enable DataFrames and RDDs to read from a tenant-specific table
> ---------------------------------------------------------------
>
>                 Key: PHOENIX-3532
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3532
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Nico Pappagianis
>             Fix For: 4.10.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Currently the method phoenixTableAsDataFrame in SparkSqlContextFunctions
> and phoenixTableAsRDD in SparkContextFunctions do not pass the tenantId 
> parameter along to the PhoenixRDD constructor. The tenantId parameter was 
> added as part of PHOENIX-3427 but was not properly implemented (by me). This 
> JIRA will fix this issue and add tests around reading tenant-specific tables 
> as both DataFrames and RDDs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to