phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Mahonin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (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 Fri, 11 Nov 2016 14:21:58 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Mahonin updated PHOENIX-3427:
----------------------------------
    Fix Version/s: 4.9.0

> 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
>             Fix For: 4.9.0
>
>
> 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