[
https://issues.apache.org/jira/browse/PHOENIX-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15655619#comment-15655619
]
ASF GitHub Bot commented on PHOENIX-3427:
-----------------------------------------
Github user jmahonin commented on the issue:
https://github.com/apache/phoenix/pull/221
Thanks @nico-pappagianis I think I've got it squared away. Your changes are
contained in the following commits:
https://github.com/apache/phoenix/commit/3886638b04a3e494be70e1e681ad56cb1c7e33c5
https://github.com/apache/phoenix/commit/3b07c2f1bad96210e9a81079aed1149f5fcb71bc
Please let me know if I missed anything. Note that I pruned some of the
whitespace-only changes to unrelated files. The unit tests pass for me though.
Thanks and well done!
> 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)
