Github user kaspersorensen commented on the pull request:
https://github.com/apache/metamodel/pull/78#issuecomment-164189119
Fixed the EOLs.
That's a very good question actually... You're right that it would override
```fs.defaultFS```, and initially that was also my intention. I see that
HADOOP_CONF_DIR and YARN_CONF_DIR has become standards used by libraries such
as Apache Spark and others. I was thinking it would be nice to reuse that
standard so that configuration in MetaModel is as easy as possible... BUT of
course you're right that it might be that the environment variable is
unintentionally set up to configure a _different_ hadoop installation. Hmm then
I guess we shouldn't check for environment variables or system properties, but
rather only use the constructor argument as a way of configuring it. Then
applications that are using MetaModel have to do their own environment variable
checking, if it's applicable in their situations.
---
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.
---
