[
https://issues.apache.org/jira/browse/PHOENIX-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Afshin Moazami updated PHOENIX-2498:
------------------------------------
Description:
When using Phoenix map reduce bulk loader to load data from a csv file to a
table (myTable) with a secondary index (myIndex) in schema (mySchema), if I use
{code} -table mySchema.myTable {code}
data will load only to the myTable, not myIndex.
But, both will be loaded if I use:
{code} -schema mySchema -table myTable {code}
I am not sure if it is a bug or feature, but it is not documented anywhere (or
at lease I couldn't find it)
As a result of the first usage (where index is not loaded), we can have weird
scenarios like
{code:xml} select /*+ INDEX(mySchema.myTable myIndex) */* from myTable where
myColumn = 'myValue'; {code}
and it returns a row that myColumn is not equal to myValue, because where
clause is validated against the index and the data will be returned from the
main table ( I guess)
was:
When using Phoenix map reduce bulk loader to load data from a csv file to a
table (myTable) with a secondary index (myIndex) in schema (mySchema), if I use
-table mySchema.myTable
data will load only to the myTable, not myIndex.
But, both will be loaded if I use:
-schema mySchema -table myTable
I am not sure if it is a bug or feature, but it is not documented anywhere (or
at lease I couldn't find it)
As a result of the first usage (where index is not loaded), we can have weird
scenarios like
select /*+ INDEX(mySchema.myTable myIndex) */* from myTable where myColumn =
'myValue'
and it returns a row that myColumn is not equal to myValue, because where
clause is validated against the index and the data will be returned from the
main table ( I guess)
> Secondary index table is not updated in bulk load
> -------------------------------------------------
>
> Key: PHOENIX-2498
> URL: https://issues.apache.org/jira/browse/PHOENIX-2498
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.5.2
> Environment: CentOs
> Reporter: Afshin Moazami
> Labels: bulkloader, secondary_index
>
> When using Phoenix map reduce bulk loader to load data from a csv file to a
> table (myTable) with a secondary index (myIndex) in schema (mySchema), if I
> use
> {code} -table mySchema.myTable {code}
> data will load only to the myTable, not myIndex.
> But, both will be loaded if I use:
> {code} -schema mySchema -table myTable {code}
> I am not sure if it is a bug or feature, but it is not documented anywhere
> (or at lease I couldn't find it)
> As a result of the first usage (where index is not loaded), we can have weird
> scenarios like
> {code:xml} select /*+ INDEX(mySchema.myTable myIndex) */* from myTable where
> myColumn = 'myValue'; {code}
> and it returns a row that myColumn is not equal to myValue, because where
> clause is validated against the index and the data will be returned from the
> main table ( I guess)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
