[
https://issues.apache.org/jira/browse/TAJO-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183644#comment-14183644
]
ASF GitHub Bot commented on TAJO-838:
-------------------------------------
Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/192#discussion_r19368310
--- Diff:
tajo-catalog/tajo-catalog-common/src/main/java/org/apache/tajo/catalog/IndexDesc.java
---
@@ -42,10 +44,11 @@ public IndexDesc() {
this.builder = IndexDescProto.newBuilder();
}
- public IndexDesc(String idxName, String databaseName, String tableName,
Column column,
+ public IndexDesc(String name, Path indexPath, String databaseName,
String tableName, Column column,
--- End diff --
This index seems to support single column index. In my opinion, you already
takes multiple sort specs. As a result, it seems to be easy to support
composite index.
> Improve query planner to utilize index
> --------------------------------------
>
> Key: TAJO-838
> URL: https://issues.apache.org/jira/browse/TAJO-838
> Project: Tajo
> Issue Type: Sub-task
> Components: planner/optimizer
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Priority: Minor
>
> Index can improve the query performance when the selectivity of query is high.
> Thus, query planner should decide whether index is used or not for a given
> query.
> The selectivity can be guessed using statistics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
