Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/tajo/pull/439#issuecomment-89555663
Thank you for telling me the behind story, @jihoonson . I didn't know the
cause of inconsistency before.
By the way, in a social coding space, I think my small codes can be
stepping stones to help someone who starts faster than me. So, we should break
our big problems into small problems as possible as we can. Don't you think so?
:)
IMO, if you open your code in your github and everyone can see your
low-performance code, Tajo will get the better performance faster. Otherwise,
you will see my or others' similar low-performance code again because nobody
knows the performance cut-line. It would be a little bit waste of community
efforts. What about making your code open, @jihoonson ?
In any way, I respect Tajo community's policy. I will keep this pull
request and move on execution logic after finishing current ORC format issue.
Warmly,
Dongjoon.
---
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.
---
