Hi Jody,
Sorry if I wasn't clear enough in my previous e-mails, I'll try to clarify.
When a mongodb collection is published and no schema already exists for it, a
schema is inferred by MongoInferredMapper and added to the schema store.
MongoInferredMapper recursively inspects all properties of the first document
in the collection and adds the corresponding attributes to the schema.
So, for the example collection described earlier a schema like the following
would be generated:
...
"attributeDescriptors" : [ {
...
{
"localName" : "data.intProperty",
...
"userData" : {
"mapping" : "data.intProperty"
}
}, {
"localName" : "data.doubleProperty",
...
"userData" : {
"mapping" : "data.doubleProperty"
}
}, {
"localName" : "data.stringProperty",
...
"userData" : {
"mapping" : "data.stringProperty"
}
} ]
I omitted the irrelevant parts. So we have both "localName" and "mapping"
containing the same piece of information, i.e. the full path to the property.
My understanding is that the "mapping" bit is perfectly fine and it's all we
need to be able to retrieve the property value from the backend; as for
"localName", it doesn't really matter what name we pick, as long as it is
unique in the context of the feature type.
My previous suggestion was to keep the current naming convention, which readily
provides unique names, but take care to replace characters which may cause
problems (for sure '.' and ':', probably only letters and numbers should be
allowed).
Another strategy could be to not use the full property path as localName, just
take the last segment and then make sure it's unique by some other means (e.g.
appending/prepending a counter).
Yet another solution I didn't think about earlier could be to leave everything
as is and clearly state in the mongodb module documentation that to be able to
filter on nested properties (and in general on attributes whose name contain
special characters) one has to enclose the attribute name in double quotes
(see:
http://docs.geoserver.org/latest/en/user/filter/ecql_reference.html#attribute )
I kind of like the "leave as is" approach, since it allows us to keep attribute
names as the user expects them.
Any further thoughts?
Best regards,
Stefano Costa
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==
Dott. Stefano Costa
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.
Da: "Jody Garnett" jody.garn...@gmail.com
A: "Stefano Costa" stefano.co...@geo-solutions.it
Cc: "Geotools-Devel list" geotools-devel@lists.sourceforge.net
Data: Mon, 6 Jul 2015 19:27:57 -0400
Oggetto: Re: [Geotools-devel] Filters on nested properties don't work in
MongoDB datastore
> Looks like we are getting past the "GeoServer's filter parameter parsing
> process" vs XPath question.
> Can I get a clarification on how MongoDB works: should it be publishing these
> as "properties.intProperty" or just "intProperty"?
> --
> Jody Garnett
> On 6 July 2015 at 08:23, Stefano Costa <stefano.co...@geo-solutions.it> wrote:
> Hi all,
>
first of all, a bit of context: with the new MongoDB community plugin,
>
it is possible to map as (simple) attributes properties that are nested
>
inside JSON objects.
>
E.g., from a collection containing documents with the following
>
structure:
>
{
>
"geometry" : {
>
"type" : "Point",
>
"coordinates" : [ 2, 2 ]
>
},
>
"data" : {
>
"intProperty" : 2,
>
"doubleProperty" : 2.2,
>
"stringProperty" : "two"
>
}
>
}
>
the default schema mapper would map the three nested properties of the
>
"data" object to three attributes named "properties.intProperty",
>
"properties.doubleProperty" and "properties.stringProperty".
>
In theory, it should be possible to apply CQL filters to the value of
>
such attributes, like "data.stringProperty LIKE 't%'": however, when the
>
filter is passed as a request parameter in a WMS request to GeoServer,
>
it doesn't work.
>
The reason is that "properties.doubleProperty" is translated to
>
"properties/doubleProperty" by ECQLCompiler (invokes
>
ECQLFilterBuilder.buildCompoundAttribute() passing it '/' as attribute
>
path separator), which makes the property a complete stranger to mongo
>
datastore's collection mapper.
>
The issue passed unnoticed through unit tests because the test code
>
builds filters simply by invoking methods on a FilterFactory2
>
implementation and doesn't go through GeoServer's filter parameter
>
parsing process, so ECQLCompiler never comes into play.
>
Now, I could easily fix the issue replacing '/' with '.' when a
>
PropertyName filter is visited, but first I'd be interested to know if
>
there's a good reason for the behavior of ECQLCompiler (and also
>
CQLCompiler, it seems), which at first sight seems a bit odd, at least
>
to me.
>
Any comment is highly appreciated.
>
--
>
Best regards,
>
Stefano Costa
>
==
>
GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
>
==
>
Dott. Stefano Costa
>
Senior Software Engineer
>
GeoSolutions S.A.S.
>
Via Poggio alle Viti 1187
>
55054 Massarosa (LU)
>
Italy
>
phone: +39 0584 962313
>
fax: +39 0584 1660272
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
-------------------------------------------------------
>
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
>
Le informazioni contenute in questo messaggio di posta elettronica e/o
>
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
>
Il loro utilizzo è consentito esclusivamente al destinatario del
>
messaggio, per le finalità indicate nel messaggio stesso. Qualora
>
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
>
cortesemente di darcene notizia via e-mail e di procedere alla
>
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
>
Conservare il messaggio stesso, divulgarlo anche in parte,
>
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
>
diverse, costituisce comportamento contrario ai principi dettati dal
>
D.Lgs. 196/2003.
>
The information in this message and/or attachments, is intended solely
>
for the attention and use of the named addressee(s) and may be
>
confidential or proprietary in nature or covered by the provisions of
>
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
>
Data Protection Code).Any use not in accord with its purpose, any
>
disclosure, reproduction, copying, distribution, or either
>
dissemination, either whole or partial, is strictly forbidden except
>
previous formal approval of the named addressee(s). If you are not the
>
intended recipient, please contact immediately the sender by
>
telephone, fax or e-mail and delete the information in this message
>
that has been received in error. The sender does not give any warranty
>
or accept liability as the content, accuracy or completeness of sent
>
messages and accepts no responsibility for changes made after they
>
were sent or for other risks which arise as a result of e-mail
>
transmission, viruses, etc.
>
------------------------------------------------------------------------------
>
Don't Limit Your Business. Reach for the Cloud.
>
GigeNET's Cloud Solutions provide you with the tools and support that
>
you need to offload your IT needs and focus on growing your business.
>
Configured For All Businesses. Start Your Cloud Today.
> https://www.gigenetcloud.com/
>
_______________________________________________
>
GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
