Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/301#issuecomment-68783286
I had have thought of some design consideration. Our direction is to make
storages pluggable. BTW, in this implementation, type validator is implemented
separately from storage format implementation. Especially, type validator is in
tajo-core. It would be better if validation and storage formation
implementations are located in some same place.
The way is to implement some class or interface to give file format
properties. But, it causes some breaking changes and takes more time. So, I
think that your patch is a nice approach right now.
Also, I'll create an issue to improve it to be on the our roadmap.
---
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.
---
