phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nico Pappagianis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3427) rdd.saveToPhoenix gives table undefined error when attempting to write to a tenant-specific view (TenantId defined in configuration object and passed to saveToPhoenix)
Date Tue, 08 Nov 2016 19:59:58 GMT

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

Nico Pappagianis commented on PHOENIX-3427:
-------------------------------------------

Thanks Josh. I implemented that change and wrote a couple tests around it.

I've refactored the IT test classes some, as the single class was starting to get unwieldy.
Let me know if it looks OK, I'll push to my branch shortly. Thanks again! Hope all is well
with your new baby :)

> 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)

Mime
View raw message