lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Bernstein (JIRA)" <>
Subject [jira] [Commented] (SOLR-9333) Add list and tup Streaming Expressions
Date Mon, 17 Apr 2017 01:46:41 GMT


Joel Bernstein commented on SOLR-9333:

I've been giving this ticket more thought lately and I have a design that I think works well.
The design is to add two new data structure expressions called *list* and *tup*. These are
based on on *Lisps* *list* and *con*.

The *tup* expression returns a single tuple based on list of key value pairs.
tup("key1", "value1". "key2", "value2")
The *list* expression is a list of Streaming Expressions in the following syntax:
list(expr, expr, expr)

The list expression will iterate from each expression in the list in order.

> Add list and tup Streaming Expressions
> --------------------------------------
>                 Key: SOLR-9333
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Cao Manh Dat
>            Assignee: Cao Manh Dat
> Currently in streaming expression, if we wanna provide a list of named/unamed parameters.
We wrap the values inside a StreamExpressionValue and manually separate value based on ','
> In order to make the streaming expression more compact and extendable, I propose new
kind of parameter to streaming expression. 
> {code}
> Map Expression Parameter : { key1 = value1, key2 = value2, .... }
> {code}
> So new tuple stream can be 
> {code}
> arrays({term=a, score=1.0}, {term=b, score=2.0})
> or
> search(collection1, q=*:*, fl="id,a_s,a_i,a_f", sort="a_f asc, a_i asc", aliases={a_i=alias.a_i,
> {code}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message