Request for community: please, test out new feature JSON queries and give us your feedback about manticoresearch

[barryhunter]

How do you run a generic full-text 'extended query'?

Wonder about

"query": {
    "match": { "_all": "one (two | three) \"four five size\"/2" }
}

But about

By default keywords are combined using the OR operator.

which seems to suggest its a simple 'bag of words' (kinda like historic SPH_MATCH_ANY) - even with AND would give unexpected results.

Or should just use /search or /sql if want general extended-syntax queries?

[tomatolog]

only /search or /sql endpoints Sphinx compatible and we also think to change reply interface for them. Any suggestions are welcome.

[barryhunter]

ok :) I suppose no benefit to migrate to /json/search, if don't want the 'alternative' query format it offers. No harm in using original /search//sql for queries, and just using /json/insert etc to maintain the Real-time Index.

Dont see what could be improved really with the reply format from /search//sql - seems simple and fine (although of course well familiar with sphinx!) - the only issue seems to be no support for multi query reply (including FACET)

[puzrin]

1. Bulks

Note that the bulk operation stops at the first query that results in an error.

On bulk inserts such behaviour may be not desired (silent fail & continue preferable). Result could be an array with statuses for each operation.

Right now our workaround in sql is use replace instead of insert - because replace does not fails on dupes.

2. Note for node.js clients and so on

JS has limitation for integer size - 56 bits max. While docid is 64 bits. I don't know if this can become a real problem, but worth to keep in mind.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Feel free to re-open the issue in case it becomes actual.