Showcase your project at ApacheCON: consider Podling Shark Tank

Hi! I apologize for the wide distribution, but since my email to general@ didn't seem to have reached all of the podling communities, I took the liberty of direct email. Here's the deal: If you are (or anybody you know who's passionate about your project is) going to travel to Vancouver for

Re: query endpoint

We could set a configurable (server-side) limit that defaults to 10, this is what ElasticSearch uses as a default. cheers, Serge… > On 25 avr. 2016, at 13:51, Thomas Draier wrote: > > Hi, > > I just noticed that when doing a query through the rest api, if no limit > was

query endpoint

Hi, I just noticed that when doing a query through the rest api, if no limit was specified in the json query, default was to return no result .. I created a ticket for that : https://issues.apache.org/jira/browse/UNOMI-26 . Do you think we should use -1 (no limit) or hardcode a specific limit to

[jira] [Created] (UNOMI-26) Query default limit is 0 (no results)

Thomas Draier created UNOMI-26: -- Summary: Query default limit is 0 (no results) Key: UNOMI-26 URL: https://issues.apache.org/jira/browse/UNOMI-26 Project: Apache Unomi Issue Type: Bug

[jira] [Assigned] (UNOMI-26) Query default limit is 0 (no results)

[ https://issues.apache.org/jira/browse/UNOMI-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Draier reassigned UNOMI-26: -- Assignee: Thomas Draier > Query default limit is 0 (no results) >

Re: custom condition types

Hmm… I struggled with that in initial designs. I think we might be possible to maybe created some kind of i18n marker to a resource or something ? The problem is that (for the moment) we haven’t addressed any i18n stuff in the spec, so we’ll have to see how we can handle that (although for the