Thanks for that - I migrated it to the correct project here GEOT-6348 <https://osgeo-org.atlassian.net/browse/GEOT-6348>
I also created a MongoDB component <https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOT%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20mongodb> in Jira so we could short list MongoDB issues. -- Jody Garnett On Tue, 23 Jul 2019 at 12:58, Artem Groznykh <[email protected]> wrote: > Hi. As you offered I created a Jira ticket > <https://osgeo-org.atlassian.net/browse/GEOS-9291?atlOrigin=eyJpIjoiOWIzOWUyYmFhMGQ1NGJjMDkzNjg3ZGRiMzU0ZjY5NmQiLCJwIjoiaiJ9> > for > this thread > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Без > вирусов. www.avast.ru > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_2422930794974714584_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > пт, 21 июн. 2019 г. в 11:51, Nuno Oliveira <[email protected] > >: > >> Hi, >> thank you for the detailed feedback, indeed at first look this looks >> like a bug to me. >> >> Can you create Jira ticket for this? Instructions: >> http://geoserver.org/issues/ >> >> Best regards, >> Nuno Oliveira >> >> On Thu, 2019-06-20 at 09:54 -0700, groznykh wrote: >> >> Hi all >> >> I use GeoServer 2.15 and MongoDB 3.6 >> >> I've created a collection with data from here >> <https://docs.geoserver.org/stable/en/user/data/app-schema/mongo-tutorial.html> >> (just two records), created 2dsphere index >> >> Then I created a layer from that collection and tried to request it by WMS >> with cql_filter in URL params. >> >> >> 1. when I use simple attributes (that are not multiple) in the filter all is >> fine (points are visible): >> >> - filter: "contract.mail" ILIKE '%@mail.com%' OR "name" ILIKE '%station%' >> >> - mongo log: { ... , filter: { }, projection: { geometry: 1, >> contact.mail: 1, name: 1 }, ... } >> >> <http://osgeo-org.1560.x6.nabble.com/file/t385081/stations-stations.png> >> >> 2. when I use attributes that are multiple in the filter then it DOES NOT >> work (there is no any point on received PNG): >> >> - filter: "measurements.name" ILIKE '%wind%' OR "measurements.unit" ILIKE >> '%c%' >> >> - mongo log: { ... , filter: { }, projection: {geometry: 1, >> measurements.unit: 1, measurements.name: 1}, ... } >> >> <http://osgeo-org.1560.x6.nabble.com/file/t385081/stations-stations_%281%29.png> >> >> 3. when I change OR to AND in previous filter then it's works fine: >> >> - filter: "measurements.name" ILIKE '%wind%' AND "measurements.unit" ILIKE >> '%c%' >> >> - mongo log: { ..., filter: { $and: [ { measurements.name: /^.*wind.*$/i >> }, { measurements.unit: /^.*p.*$/i } ] }, projection: { geometry: 1 }, ... } >> >> <http://osgeo-org.1560.x6.nabble.com/file/t385081/stations-stations_%282%29.png> >> >> So I concluded that GeoServer does AND operation by sending filter to >> mongoDB. And OR operation by itself requesting all records from collection. >> But with attributes that are multiple something goes wrong. I think it's a >> bug. >> >> If you have any sugestions please tell me. >> >> >> >> -- >> Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-Dev-f3819232.html >> >> >> _______________________________________________ >> Geoserver-devel mailing >> [email protected]https://lists.sourceforge.net/lists/listinfo/geoserver-devel >> >> -- >> Regards, >> Nuno Oliveira >> == >> GeoServer Professional Services from the >> experts! >> Visit http://goo.gl/it488V for more information. >> == >> >> Nuno Miguel Carvalho Oliveira >> @nmcoliveira >> Software Engineer >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> http://www.geo-solutions.ithttp://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. >> >> > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Без > вирусов. www.avast.ru > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_2422930794974714584_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
