Mailing-List: contact dev-help@asterixdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.apache.org
MIME-Version: 1.0
From: Chen Luo <cluo8@uci.edu>
Date: Wed, 27 Sep 2017 20:43:27 -0700
Message-ID: <CAEGOuq0QFZRtBWnR9dm-J00a7W1GF2VikuF=wC3hJaXFReFoWA@mail.gmail.com>
Subject: Question about AsterixDB Functions
To: dev@asterixdb.apache.org
Content-Type: multipart/alternative; boundary="001a114a9c6615563d055a37b6f1"
archived-at: Thu, 28 Sep 2017 03:43:34 -0000

--001a114a9c6615563d055a37b6f1
Content-Type: text/plain; charset="UTF-8"

Hi Devs,

Recently I was facing a problem with the IntersectOperator. Previously
we've used the IntersectOperator to intersects primary keys returned from
searching multiple secondary indexes, and use them to perform primary key
lookups. However, with component Id-based acceleration, each primary key
returned from a secondary index would carry a component Id (which is two
numbers). Thus, inside the IntersectOperator, we only intersect the primary
keys, while need to select a proper component Id based on these inputs. For
example, for 3 input tuples (a, [1, 3]), (a, [0, 2]) and (a, [2, 2]), where
'a' is the primary key and the interval is the component Id, we may return
(a, [2, 2]) as the output of the intersection.

Thus, my question is that *is there any function interface inside AsterixDB
which takes a list of input tuples and produce a tuple as a result*? With
this functionality, we can devise strategies to select the best component
Id for each primary key. Any help is appreciated!

Best regards,
Chen Luo

--001a114a9c6615563d055a37b6f1--