Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/377#issuecomment-77556909
@sirpkt thanks for your work.
I have a couple of comments.
First, ```CSVFILE_DELIMITER``` is deprecated. If there are any bugs related
to ```TEXT_DELIMITER```, we must fix it instead of using
```CSVFILE_DELIMITER```.
In addition, I have a question about the following your description.
```
Without this, when two tables, one is 'csvfile.delimiter'=';' and the other
has no option, are used in the same query, one is set as TEXT_DELIMITER = ';'
and the other is set as TEXT_DELIMITER = '|' and compete for the meta option of
the Execution block.
```
If only one table is configured with an explicitly different delimiter, two
tables must be parsed with different delimiters. If I misunderstand anything,
please let me know.
Second, it is hard to unserstand for me why ```CSVFILE_DELIMITER``` or
```TEXT_DELIMITER``` is required to store intermediate results. As you know,
the default file type of intermediate results is ```RAW```, not ```CSV``` or
```TEXT```.
Would you mind explaining more detailed backgrounds?
---
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.
---
