[
https://issues.apache.org/jira/browse/RYA-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596236#comment-15596236
]
ASF GitHub Bot commented on RYA-174:
------------------------------------
Github user isper3at commented on the issue:
https://github.com/apache/incubator-rya/pull/118
I disagree with the notion of matching accumulo naming conventions. I'm
fine with ambiguous naming in interfaces and during design, but altering naming
to match another datastore just seems.....wrong? If we want consistency, lets
use what flapdoodle calls it. Then we already have the correct naming if we
need to google something.
> 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)
