carbondata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From simafengyun <>
Subject [GitHub] incubator-carbondata issue #627: CARBONDATA-748
Date Tue, 07 Mar 2017 11:20:44 GMT
Github user simafengyun commented on the issue:
    so binary search only fit the below cases,please comfirm thanks
    1 the first dimension column , since it's logicl order are the same with physical order
in blocklet level,so it does not need inverted index
    2 for dimension column which has inverted index
    question 1
    if a dimension column is not the first colmn and in a blocklet it just has the same order
for both logical and physical,will carbondata create inverted index for it?
    question 2
    is there an easy way to identify whether a dimension column has no_inverted_index property
config by user in source code ,so it will be helpful for me to add a condition to use binary
    在 2017-03-07 18:35:05,"Ravindra Pesala" <> 写道:
    @simafengyun you are right, default we sort the data but we can avoid sorting using no_inverted_index
property at tblproperties level. So if user uses this configuration then we cannot do binary
search always.
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on GitHub, or mute the thread.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message