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

Gabriel Reid updated PHOENIX-1248:
----------------------------------
    Attachment: PHOENIX-1248b.patch

[~rajeshbabu], I finally took a look at this, sorry for taking so long.

I've uploaded a slightly alternate patch that (I think) simplifies things by 
simply using the physical index table name when originally building up the list 
of index tables, instead of adding an additional configuration parameter for 
the job, etc. 

This patch also has the impact that the physical index table name (and not the 
logical index name) is to be supplied with the --index-table option. I see this 
as an improvement, as the option is called "index-table" and not "index-name".

The patch also includes a test where a local index is loaded together with the 
core table content.

Can you take a look and let me know what you think?

> CsvBulkLoadTool is failing with IAE when local index specified for 
> --index-table parameter
> ------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-1248
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1248
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.1
>            Reporter: rajeshbabu
>            Assignee: Rajeshbabu Chintaguntla
>             Fix For: 5.0.0, 4.3
>
>         Attachments: PHOENIX-1248.patch, PHOENIX-1248b.patch, p1248_0.log
>
>
> {code}
> 14/09/11 22:38:11 INFO mapreduce.HFileOutputFormat2: Writing partition 
> information to /tmp/partitions_81e2ee23-836c-4eae-b413-ac6bd6a96623
> 14/09/11 22:38:11 ERROR mapreduce.CsvBulkLoadTool: Import job on 
> table=TEST_IDX failed due to exception:java.lang.IllegalArgumentException: No 
> regions passed
> 14/09/11 22:38:11 INFO client.HConnectionManager$HConnectionImplementation: 
> Closing zookeeper sessionid=0x148123145090287
> {code}



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

Reply via email to