Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 957C8200D68 for ; Thu, 14 Dec 2017 06:19:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 93D8B160C24; Thu, 14 Dec 2017 05:19:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DBC80160C23 for ; Thu, 14 Dec 2017 06:19:04 +0100 (CET) Received: (qmail 97362 invoked by uid 500); 14 Dec 2017 05:19:04 -0000 Mailing-List: contact dev-help@olingo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@olingo.apache.org Delivered-To: mailing list dev@olingo.apache.org Received: (qmail 97351 invoked by uid 99); 14 Dec 2017 05:19:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Dec 2017 05:19:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 83483C0D33 for ; Thu, 14 Dec 2017 05:19:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id vhp70kaFXNYw for ; Thu, 14 Dec 2017 05:19:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id E7D7E5F296 for ; Thu, 14 Dec 2017 05:19:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D72F7E0F88 for ; Thu, 14 Dec 2017 05:19:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 32EAD212FE for ; Thu, 14 Dec 2017 05:19:00 +0000 (UTC) Date: Thu, 14 Dec 2017 05:19:00 +0000 (UTC) From: "Ramya (JIRA)" To: dev@olingo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (OLINGO-1144) How to use the FilterFactory to create a valid URI for filtering on a ComplexValue in a collection? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 14 Dec 2017 05:19:05 -0000 [ https://issues.apache.org/jira/browse/OLINGO-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramya resolved OLINGO-1144. --------------------------- Resolution: Fixed > How to use the FilterFactory to create a valid URI for filtering on a ComplexValue in a collection? > --------------------------------------------------------------------------------------------------- > > Key: OLINGO-1144 > URL: https://issues.apache.org/jira/browse/OLINGO-1144 > Project: Olingo > Issue Type: Question > Components: odata4-client > Affects Versions: (Java) V4 4.3.0 > Reporter: Geert Graat > > Hi, > We use the Olingo client library to call an OData service (which also uses the Olingo library). We are implementing filtering using the {{FilterFactory}}. The problem we are facing is how we can build a valid URIFilter to filter on the values of a ComplexType that is inside a collection. > Below is a simplified version of or metadata document: > {code} > > > > > > > > > > > > > > > > > > {code} > What we want is for instance to filter on an Entity that has a Value with name 'example'. For this we need to construct the following URI: > {code}$filter=values/any(v:v/name eq 'example'){code} > We need to use the {{any}} function because as you can see from the metadata model an {{Entity}} can contain multiple {{Value}} complex types in the collection property {{values}}. > The problem is the definition of the lambda variable ({{v}} in the example above). If we use the {{FilterFactory}}, we can get a {{FilterArgFactory}} that has an {{any}} function. This creates a {{FilterLambda}} with the following arguments: > * collection: the property that contains the collection, in our case {{values}} > * operator: the operator, in our case {{any}} > * expression: the expression to filter on our collection, in our case {{v/name eq 'example'}} > So where does the declaration of the lambda variable go? We have searched the entire library, but cannot find it. Can you please help with an example? -- This message was sent by Atlassian JIRA (v6.4.14#64029)