[
https://issues.apache.org/jira/browse/RYA-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602692#comment-15602692
]
ASF GitHub Bot commented on RYA-174:
------------------------------------
Github user pujav65 commented on the issue:
https://github.com/apache/incubator-rya/pull/118
i thought the mongo connections factory was a bad idea at the time. so i
think removing it is a good thing in general. The instance driver you're
referring to is in the merge tool -- its not used in the main client path. The
accumulo dao has a setConnector() method which really should have been emulated
by the Mongo dao. I didn't realize the pattern until we started having issues
with setting up multiple connections, but the passing in the connector/client
pattern is nice because its a lot more flexible than what we currently have.
Regardless, I think this pull request is fine -- all of this discussion is on
future direction.
> Embedded Mongo tries to bind to busy ports
> ------------------------------------------
>
> Key: RYA-174
> URL: https://issues.apache.org/jira/browse/RYA-174
> Project: Rya
> Issue Type: Bug
> Reporter: Aaron Mihalik
> Assignee: Aaron Mihalik
> Fix For: 3.2.10
>
>
> There are a couple mongo tests that fail while building on builds.a.o. It
> looks like Embedded Mongo will try to bind to ports that are already in use.
> https://builds.apache.org/view/Incubator%20Projects/job/incubator-rya-master/org.apache.rya$rya.indexing/31/testReport/junit/mvm.rya.indexing.mongo/MongoGeoIndexerSfTest/testIntersectsLine/
> https://builds.apache.org/view/Incubator%20Projects/job/incubator-rya-master/org.apache.rya$rya.indexing/31/testReport/junit/mvm.rya.indexing.mongo/MongoTemporalIndexerTest/testQueryInstantHasBeginningInterval/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
