I am out this week, I am alarmed if geoserver has custom parameter
implementation. It should be a straight up data structure.
When parsing from xml we should have access to better namespace information
from the XML document beyond what can be represented in CQL.
Perhaps you need to translate the Xpath expression used by the filter
parameterName data structure to match your data store internals? That would
be a new feature ...
Jody
On Mon, Jul 6, 2015 at 8:37 AM Andrea Aime <andrea.a...@geo-solutions.it>
wrote:
> On Mon, Jul 6, 2015 at 2:23 PM, 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.
>>
>
> a.b is translated to a xpath meaning "the b property of the a attribute".
> Changing this behavior might break existing users of WFS 2.0 joins (which
> use a syntax like alias/property to refer to a property
> of one of the feature types being joined).
>
> Wondering if the mongo store can be changed instead?
>
> Cheers
> Andrea
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> 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
>
--
--
Jody Garnett
------------------------------------------------------------------------------
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
