Hi Miguel,
Thanks for the logs. The exception is happening during some
metadata retrieval.
If you are willing to do a little more digging, providing the data
in that table before you wipe it might help us out. There should be
an combiner set on that table which would aggregate the keys for
which there was an issue. The two diagnostics you could do are...
1. Scan the bounds table and send along the output.*
2. Send along the output of 'config -t GEOMESA_RASTER_BOUNDS'.
With that info, we'd be able to see if the issue is with the
combiner or with the data ingest. I have put in a ticket in our
JIRA here https://geomesa.atlassian.net/browse/GEOMESA-938.
Depending on what the underlying cause is, we should be able to cook
up a work around.
Thanks,
Jim
* If the 'scan' command returns several screens, you can do the
following:
Create a file (say /tmp/script) with lines like this:
table GEOMESA_RASTER_BOUNDS
scan -np
exit
And then run
> accumulo shell -u user -p pass -f /tmp/script >
/tmp/rasterOutput.txt
Accumulo's shell will execute the commands in the file given, and
the -np on the scan will turn off pagination.
On 10/29/2015 01:42 PM, Miguel Ángel
Esbrí wrote:
Hi Jim,
The
geoserver logs are attached to the email.
Thank
you very much for the support :)
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users
|