Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/231#issuecomment-68293902
It's excellent. It's works very well. It's performance gain was larger than
I expected. I definitely think that this feature is very promising. Probably,
this feature may differentiate Tajo from other competitive systems.
The objective of following questions is to make this feature more solid and
more consistent.
While I'm testing features on a local cluster, I get some questions.
In some tests, CREATE INDEX statement includes physical properties as the
following example:
```
create index l_orderkey_idx on lineitem (l_orderkey asc null first);
```
How does a specified sort order affects index creation? I tested it with
```asc``` as well as ```desc```. But, it works well in both cases. Is it just a
hint?
In addition, such a physical property is fragile due to following reasons:
* It is hard for users to ensure the table properties.
* INSERT (OVERWRITE) INTO AS SELECT can change the physical properties.
How do you think about them? After I get your answer, I'll give additional
questions.
Also, I have feature wish.
* There is no way to show already created indexes and their information.
---
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.
---
