Github user blrunner commented on the pull request:
https://github.com/apache/tajo/pull/624#issuecomment-127275276
I found that this patch run as expected with HiveCatalogStore and
MySQLStore on my testing cluster. And simple query response had been reported
as following:
* Table schema:
```
create table partitioned_lineitem (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)
partition by column (L_ORDERKEY bigint, L_PARTKEY bigint)
```
* Partition numbers: 100,000
* Select statement: select * from partitioned_lineitem limit 10;
* Response time:
- previous rewriter: 15 ~ 16 sec
- improved rewriter: 12 ~ 13 sec
Honestly, I didn't implement unit test cases for executing queries because
current almost tajo unit cases operate on MemStore. If we apply DerbyStore to
some unit test cases for physical operator, we would make a lot of effort. It
seems not to be the scope of this patch. So, I just added unit test cases for
verifying direct sql. But if you want to test this patch with build commands,
you can test with `-Dtajo.catalog.store.class` parameter as following:
```
mvn clean install -Pparallel-test -DLOG_LEVEL=WARN -Dmaven.fork.count=2
-Dtajo.catalog.store.class=org.apache.tajo.catalog.store.DerbyStore
```
---
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.
---
