Github user blrunner commented on the pull request:
https://github.com/apache/tajo/pull/651#issuecomment-124374074
OK, No problem. :-)
And if there is a message when executing *explain* command on tsql, this
patch would be more good. Currently, I can't know whether index scan is applied
or not before executing select statement as following:
```
default> create external table lineitem (L_ORDERKEY bigint, L_PARTKEY
bigint, L_SUPPKEY bigint, L_LINENUMBER bigint, L_QUANTITY double,
L_EXTENDEDPRICE double, L_DISCOUNT double, L_TAX double, L_RETURNFLAG text,
L_LINESTATUS text, L_SHIPDATE text, L_COMMITDATE text, L_RECEIPTDATE text,
L_SHIPINSTRUCT text, L_SHIPMODE text, L_COMMENT text) using text with
('textfile.delimiter'='|') location 'hdfs://localhost:9010/tpch/lineitem';
OK
default> create index l_orderkey_idx on lineitem (l_orderkey);
default> \set INDEX_ENABLED true
default> explain select count(*) from lineitem where l_orderkey = 1;
explain
-------------------------------
GROUP_BY(3)()
=> exprs: (count())
=> target list: ?count (INT8)
=> out schema:{(1) ?count (INT8)}
=> in schema:{(0) }
(5 rows, 0.034 sec, 0 B selected)
default> select count(*) from lineitem where l_orderkey = 1;
Progress: 100%, response time: 0.581 sec
?count
-------------------------------
6
(1 rows, 0.581 sec, 2 B selected)
```
---
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.
---
