GitHub user okram opened a pull request:
https://github.com/apache/incubator-tinkerpop/pull/258
TINKERPOP-1217: Repeated Logging of "The HadoopPools has not been
initialized, using the default pool"
https://issues.apache.org/jira/browse/TINKERPOP-1217
This is a simple fix. However, the more troubling thing for me (and what
could be another ticket) is why are you (@rspitzer) getting that? I don't know
where in Spark the pool isn't being initialized and I haven't seen that in my
experiments with Friendster/etc.
Perhaps we can discuss on the mailing list about where in Spark this WARN
is popping up for you.
For this issue VOTE +1.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-tinkerpop TINKERPOP-1217
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-tinkerpop/pull/258.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #258
----
commit 035dc36f4c0f077963949b5222650ee7b4497533
Author: Marko A. Rodriguez <okramma...@gmail.com>
Date: 2016-03-11T14:43:43Z
If the HadoopPool hasn't been initlized, then initialize it with a default
configuration. This ensures that this WARN happens once and only once. The more
troubling issue, is why is the HadoopPool isn't getting initlized for @rspitzer
in Spark, but that is another ticket.
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
