Re: [geomesa-dev] accumulo 1.6 branch.

[Jim Hughes <jnh5y@xxxxxxxx>]

Alex,

There are no requirements for that test to run, so we needn't let it block us.  I believe that test is solely aimed at exercising the function GeoMesaDataStoresPage.getTableMetadata.

Potentially, if the test is failing, but may be repairable, you might give pendingUntilFixed a spin.*

Jim

*  As an example in the GeoMesa codebase: https://github.com/locationtech/geomesa/blob/accumulo1.5.x/1.x/geomesa-utils/src/test/scala/org/locationtech/geomesa/utils/time/RichIntervalTest.scala#L43-45

I like pendingUntilFixed since it is indicates intended/preferred behavior which is not yet attained.

On 01/02/2015 04:02 PM, Alex Hurd wrote:

This is what I am getting on the 1.5.x /master:

$ cd geomesa-plugin

$ mvn test

-------------------------------------------------------

 T E S T S

-------------------------------------------------------

Running org.locationtech.geomesa.plugin.ui.GeoMesaDataStoresPageTest

[2015-01-02 15:59:08,831]  WARN org.apache.accumulo.core.client.impl.ServerClient: There are no tablet servers: check that zookeeper and accumulo are running.

The test seems to launch 'zookeeper' that is using IPV6 and the test is trying to connect with IPV4?

Are there any external requirements for this test to run?

-alex

On Fri, Jan 2, 2015 at 1:03 PM, Jim Hughes <jnh5y@xxxxxxxx> wrote:

Hi Alex,

Hmm... I'm surprised by that.  I haven't used the MiniAccumuloCluster recently, and I don't remember that behavior. 

Could you push a branch to your GeoMesa fork and link to it?  I'd be happy to look at it briefly.

Thanks,

Jim

On 01/02/2015 12:13 PM, Alex Hurd wrote:

Jim,

I am having issue with MiniAccumuloCluster in the test for the DataStore on CentOS 6.6. It seems to generate a zookeeper service using IPV6 and the test is failing to connect 'localhost:port' and skips the test. Any thoughts?

Thanks,

-alex

On Fri, Jan 2, 2015 at 11:56 AM, Andrew Hulbert <ahulbert@xxxxxxxx> wrote:

We should call it accumulo1.6.x/1.x :)

On 01/02/2015 11:46 AM, Jim Hughes wrote:

Hi all,

Emilio, it would be great to keep a single branch, and I'm not sure it is the 'Maven way'. 

What's the name of the 1.6 branch?  And Alex, is there anything else we can do to help you get started?

Thanks,

Jim

On 12/22/2014 09:36 AM, Emilio Lahr-Vivaz wrote:

It would be great if we could keep a single branch and just use maven profiles to control the accumulo version. I tried changing the pom to use 1.6.0, and the places that failed were:

org.locationtech.geomesa.core.iterators.TimestampRangeIterator
org.locationtech.geomesa.core.util.ExplainingScanner
org.locationtech.geomesa.jobs.scalding.AccumuloScheme
org.locationtech.geomesa.plugin.ui.GeoMesaDataStoresPage
org.locationtech.geomesa.tools.AccumuloProperties

It might not be feasible to keep a single branch, but it's worth a try.

Thanks,

Emilio

On 12/21/2014 10:49 PM, Andrew Hulbert wrote:

Usually IntelliJ 13 though we are trying 14. Maven 3.2.3 and Java 1.7.

Andrew

On 12/21/2014 08:06 PM, Alex Hurd wrote:

thanks... is there a particular IDE/dev environment that you guys use with maven?

On Sun, Dec 21, 2014 at 5:48 PM, Anthony Fox <anthony.fox@xxxxxxxx> wrote:

There is now. ;)

Seriously, though, we need to roll out a 1.6 branch ASAP.  It would be nice if we can drop the classifier on the artifacts too.

> On Dec 21, 2014, at 3:50 PM, Alex Hurd <hurdad@xxxxxxxxx> wrote:
>
> Any plans for an accumulo 1.6 branch? I can help.
>
> -alex
> _______________________________________________
> geomesa-dev mailing list
> geomesa-dev@xxxxxxxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> http://locationtech.org/mailman/listinfo/geomesa-dev
_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev

_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev