[
https://issues.apache.org/jira/browse/CARBONDATA-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ravindra Pesala updated CARBONDATA-190:
---------------------------------------
Fix Version/s: 0.1.1-incubating
0.2.0-incubating
> Data mismatch issue
> -------------------
>
> Key: CARBONDATA-190
> URL:
https://issues.apache.org/jira/browse/CARBONDATA-190> Project: CarbonData
> Issue Type: Bug
> Reporter: kumar vishal
> Assignee: kumar vishal
> Fix For: 0.2.0-incubating, 0.1.1-incubating
>
>
> Issue steps:1. create table , then restart the server and then do data load, in that case filter query record count is not matching.
> Problem: When user is creating any table and if user has not disabled inverted index false for any key column we are setting the inverted index true in column schema object. As we are not persisting this information in schema file, so after restarting the server useInvertedIndex property is false in columnschema object and in data loading column data is not sorted and in filter execution we are doing binary search, as data is not sorted binary search is failing and it is skipping some of the record.
> Solution : In this pr default value is set to true. One more PR will be raised to handle inverted index disabled scneario. By default Inverted index will be enabled for all the column for better query performance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
