Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/231#issuecomment-68331921
@hyunsik, thanks for your comment.
Here are my answers.
1. On physical properties: When creating a BST index, the index keys are
sorted. The sort specifications in the ```CREATE INDEX``` statement are used to
specify the sort order of index keys. Maybe, we can use this feature for
performance boost of some other operations such as merge sort or sort-merge
join.
Since the sort specifications represent the sort order of index keys in a
newly created index, I think that users can specify their preferred sort
specifications which will be beneficial for future queries.
2. On the index maintenance issue: If a base table is changed, every index
created on that table must be updated. To handle this problem, we need to
introduce a new feature, such as the trigger of database systems. However,
since this will induce a huge amount of work, it would be better to proceed in
another issue. Until that, we may leave the index maintenance problem to users.
IMHO, since this feature is still experimental, it would be enough.
3. On showing index information: you can see information about the created
indexes when executing the ```\d [tablename]``` command. Of course, we need to
show more detailed information in future. I'll add this to our documentation,
too.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
