Hi
Jim,
Thank
you for your suggestions. After raising the log level we
found out that our metadata were broken. (We've migrated our
data from parquet to orc). After re-generating them using
geomesa-fs manage-metadata, everything seems to work fine
now.
It's
still a bit unclear why the CLI and the GeoMesa-GeoTools API
worked, though.
Anyway,
thank you very much!
Christian
Hi Christian,
Let's see... given what you have said, we know that
GeoServer can connect to the filesystem and read data. The
metadata is written in JSON, and it is unclear if reads for
ORC are working or not.
I'd probably start looking for a classpath issue with the ORC
dependencies. If you haven't already, I'd review the
GeoServer logs for any exceptions.
Additionally, I have a few other suggestions to try:
1. Turn on logging for org.locationtech.geomesa.fs.* in
GeoServer. GeoMesa has debug level logging[a] which will
explain which files it is opening, etc. You can enable that
in GeoServer; these pages should help get that going:
https://docs.geoserver.org/latest/en/user/configuration/globalsettings.html
https://docs.geoserver.org/latest/en/user/configuration/logging.html
2. There may be a bug in reading the data from the ORC
format. (I did check JIRA(b), but didn't find any known
bugs.)
To check this out, I'd suggest finding a small and simple
dataset (say a shapefile) and ingesting that into the same
Filesystem. If you cannot pull that data out in GeoServer, it
might give further info.
3. Even though the GeoMesa commandline tools are working, it
may be worth double-checking the GeoMesa logs to make sure
that there isn't an exception there. (This is somewhat
unlikely, but it is quick to check.)
I hope some of those suggestions help. Let us know what you
find!
Cheers,
Jim
a.
https://github.com/locationtech/geomesa/blob/geomesa_2.11-2.3.0/geomesa-fs/geomesa-fs-storage/geomesa-fs-storage-common/src/main/scala/org/locationtech/geomesa/fs/storage/common/AbstractFileSystemStorage.scala#L94-L109
b. JIRA Issues affecting version 2.3.0:
https://geomesa.atlassian.net/issues/?jql=affectedVersion%20%3D%202.3.0
Hi GeoMesa Users!
We're experiencing an
issue with GeoMesa in combination with GeoServer using the
file system data store (and the GeoMesa FS Plugin
accordingly).
Our setup:
* GeoMesa 2.3.0
* GeoServer 2.14.4
* Filesystem datastore
** encoding: orc
** partition scheme:
daily,xz2-8bits
** leaf-storage: true
What works:
* Writing, reading and
querying data using the GeoMesa GeoTools API
* Writing, reading and
querying data using the CLI (geomesa-fs)
What doesn't work:
* Querying data using
the GeoMesa-FS plugin for GeoServer
We can successfully
create a data store in GeoServer and it successfully
recognizes the feature types stored in it. Furthermore, we
can successfully publish those features as GeoServer
layers. However when it comes to visualizing the feature,
e.g. using GeoServer's layer preview feature or an
external tool like QGis, no features are returned. A WFS
response (similar for WMS) for a small test feature set
looks like this:
{"type":"FeatureCollection","features":[],"totalFeatures":2719,"numberMatched":2719,"numberReturned":0,"timeStamp":"2019-07-01T16:00:33.301Z","crs":null}
Does someone have a
clue what is going wrong here?
Thanks!
Mit freundlichen Grüßen / Kind regards
Christian Sickert
Crowd Data & Analytics for Automated Driving
Daimler AG - Mercedes-Benz Cars Development - RD/AFC
+49 176 309
71612
christian.sickert@xxxxxxxxxxx
If you are not the addressee, please inform us immediately
that you have received this e-mail by mistake, and delete
it. We thank you for your support.
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/geomesa-users
