|
As a note, if you don't have a spatial component to your row keys, spatial queries are unlikely to be very performant regardless of what you do. The advantage of ingesting the data through GeoMesa is that it will use spatially-enabled row keys, and then query
them appropriately based on GeoTools/CQL predicates.
Thanks,
Emilio Lahr-Vivaz
General Atomics, CCRi
From: geomesa-dev <geomesa-dev-bounces@xxxxxxxxxxx> on behalf of Simone Giannecchini via geomesa-dev <geomesa-dev@xxxxxxxxxxx>
Sent: Monday, October 7, 2024 9:26 AM
To: James Hughes <jnhuva@xxxxxxxxx>
Cc: Simone Giannecchini <simone.giannecchini@xxxxxxxxxxxxxxxxxxxxx>; Geomesa project developer mailing list <geomesa-dev@xxxxxxxxxxx>
Subject: -EXT-Re: [geomesa-dev] Question About Catalog Requirement in GeoMesa Cassandra DataStore
WARNING: This message is from an external source. Evaluate the message carefully BEFORE clicking on links or opening attachments.
Dear James,
thanks for taking the time to respond so quickly to this email.
We will discuss internally what to do next and let you know.
Regards,
Simone Giannecchini
==
Online training classes for GeoNode, GeoServer and MapStore from the experts!
Visit https://www.geosolutionsgroup.com/professional-training/ for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director GeoSolutions Italy
President GeoSolutions USA
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
US: +1 (845) 547-7905
https://www.geosolutionsgroup.com
https://twitter.com/geosolutions_it
-------------------------------------------------------
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying,
dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
Hi Simone!
Since GeoMesa writes its own index structure and uses its own serialization for values, you won't be able to use GeoMesa directly for an existing table.
There may be some library code which is useful for connecting to Cassandra, but other than that... I doubt you'd be able to use things as is.
Does the existing table have a spatial index of some sort? There may be some involved way to extend GeoMesa. With details, we may be able to suggest things. By the time you do that, it may be faster to write a Datastore from scratch.
Cheers
Jim
Hi James,
thanks for taking the time to respond to this.
I guess the whole point is to understand whether or not we can use GeoMesa to serve data through GeoServer from an existing Cassandra table (made of points, btw).
The table has been created outside of GeoMesa and is controlled by another tool; we would like to expose it via OGC using GeoMesa and GeoServer.
Looking forward to reading your feedback.
Regards,
Simone Giannecchini
==
Online training classes for GeoNode, GeoServer and MapStore from the experts!
Visit https://www.geosolutionsgroup.com/professional-training/ for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director GeoSolutions Italy
President GeoSolutions USA
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
US: +1 (845) 547-7905
https://www.geosolutionsgroup.com
https://twitter.com/geosolutions_it
-------------------------------------------------------
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying,
dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
Hi James,
thanks for taking the time to respond to this.
I guess the whole point is to understand whether or not we can use GeoMesa to serve data through GeoServer from an existing Cassandra table (made of points, btw).
The table has been created outside of GeoMesa and is controlled by another tool; we would like to expose it via OGC using GeoMesa and GeoServer.
Looking forward to reading your feedback.
Regards,
Simone Giannecchini
==
Online training classes for GeoNode, GeoServer and MapStore from the experts!
Visit https://www.geosolutionsgroup.com/professional-training/ for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director GeoSolutions Italy
President GeoSolutions USA
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
US: +1 (845) 547-7905
https://www.geosolutionsgroup.com
https://twitter.com/geosolutions_it
-------------------------------------------------------
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying,
dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
Hi Alessio,
Did you create the table using GeoMesa or some other method?
If you created them on your own, the data may not be written in a compatible format.
Cheers,
Jim
Dear all,
Dear Emilio,
First of all, thank you for your response. I’m replying directly to the mailing list because, for some reason, I did not receive your email directly in my inbox. I had to check the Eclipse mailing list archive to see if there had been any replies to my initial
questions.
Regarding the use case I mentioned, we need to access tables in Cassandra that reside at the root level, meaning they do not have any prefix associated with them. Could you please provide more clarification on how this can be handled in the current setup?
Additionally, I would like to ask for more details about your statement: "The catalog table is used to store the metadata about feature types, so we would need some alternative storage location if we removed it." Are you referring to the
Metadata class that maintains the list of available tables in the catalog? If so, how would you suggest managing metadata for feature types without relying on this catalog table?
Thank you again for your assistance, and I look forward to any further insights you can provide on these points.
Dear GeoMesa community,
First of all, thank you for your incredible work! I’m excited to be part of this community and appreciate the effort that goes into maintaining GeoMesa.
Recently, I’ve been experimenting with GeoServer 2.24.x and Cassandra. I successfully configured the DataStore and connected it to Cassandra using your plugin, which worked perfectly.
However, I noticed that the DataStore requires setting a catalog as a mandatory parameter, which prevents linking tables directly to the root keyspace. After a quick review of the code, it seems like making this parameter optional might not be too difficult.
Could you provide some insight into why the catalog is required? Are there any reasons or potential issues that would arise if this requirement were made optional? If this is something the community would find useful, I’d be happy to explore contributing
a solution.
Thanks again for all the great work!
Best regards,
Alessio.
--
Regards,
Alessio Fabiani
==
GeoServer Professional Services from the experts!
Visit
http://bit.ly/gs-services-us
for more information.
==
Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead
GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686
https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
-------------------------------------------------------
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione
dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore,
è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that
is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is
prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
--
Regards,
Alessio Fabiani
==
GeoServer Professional Services from the experts!
Visit
http://bit.ly/gs-services-us
for more information.
==
Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead
GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 331 6233686
https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
-------------------------------------------------------
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione
dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore,
è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that
is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is
prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/geomesa-dev
_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/geomesa-dev
_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/geomesa-dev
|
