[
https://issues.apache.org/jira/browse/PHOENIX-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655300#comment-15655300
]
ASF GitHub Bot commented on PHOENIX-3427:
-----------------------------------------
Github user nico-pappagianis commented on the issue:
https://github.com/apache/phoenix/pull/221
Thanks James. I did the following:
from my local branch:
git pull --rebase origin master
git push origin multiTenantSaveToPhoenixRDDFix
On Thu, Nov 10, 2016 at 2:01 PM, James Taylor <[email protected]>
wrote:
> *@JamesRTaylor* commented on this pull request.
> ------------------------------
>
> In phoenix-spark/src/main/scala/org/apache/phoenix/spark/
> ProductRDDFunctions.scala <https://github.com/apache/phoenix/pull/221>:
>
> > import scala.collection.JavaConversions._
>
> class ProductRDDFunctions[A <: Product](data: RDD[A]) extends Logging
with Serializable {
>
> def saveToPhoenix(tableName: String, cols: Seq[String],
> - conf: Configuration = new Configuration, zkUrl:
Option[String] = None)
> + conf: Configuration = new Configuration, zkUrl:
Option[String] = None, tenantId: Option[String] = None)
>
> Just do a git pull --rebase origin master on your local branch to pick up
> what Josh committed. Then push your next commit to your repro (either in
> the pull request or a new one).
>
> Another way would be to just stash the changes for your last commit, get
> the latest by doing a git pull origin master, then apply your stashed
> change, and push out to this pull request.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/phoenix/pull/221>, or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/ABdNQPuw52gBNzaLBxTyA2ipl6EwIrzNks5q85QngaJpZM4Krmym>
> .
>
> rdd.saveToPhoenix gives table undefined error when attempting to write to a
> tenant-specific view (TenantId defined in configuration object and passed to
> saveToPhoenix)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-3427
> URL: https://issues.apache.org/jira/browse/PHOENIX-3427
> Project: Phoenix
> Issue Type: Bug
> Reporter: Nico Pappagianis
>
> Although we can read from a tenant-specific view by passing TenantId in the
> conf object when calling sc.phoenixTableAsRDD the same does not hold for
> rdd.saveToPhoenix. Calling saveToPhoenix with a tenant-specific view as the
> table name gives a table undefined error, even when passing in the TenantId
> with the conf object.
> It appears that TenantId is lost during the execution path of saveToPhoenix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
