I saw the second post--the first post was new to me. We plan on connecting with those people later on, but right now, I'm trying to write a stop-gap dtSearch compiler until we can at least secure the funding we need to employ their help.
Right now, I have a very functional query parser, with just a few holes needing to be patched. I rewrote my AND NOT and OR NOT queries. Now I'm perplexed why this query is not working as expected: spanNear([ spanNear([field:one, field:thousand, field:one, field:hundred], 0, true), spanNot(field:thirty, spanOr([field:six, field:seven]), 2147483647, 2147483647) ], 0, true) is returning 1130..1139. expected:<[1130, 1131, 1132, 1133, 1134, 1135, 1138, 1139]> but was:<[1130, 1131, 1132, 1133, 1134, 1135, 1136, 1137, 1138, 1139]> I would've expected 1136 and 1137 to have been excluded. Original dtSearch string: "one thousand one hundred" pre/0 (thirty and not (six or seven)) I even tried it with pre/5 to see if there was something funny going on with that, but it gave the same results: 1130..1139. If you can tell me what it should look like when the SpanQuery is converted to a string, I should be able to figure out the rest. Perhaps I'm misunderstanding the pre/post parameters? Thank you for any help! On Tue, Jun 21, 2016 at 9:46 AM, Allison, Timothy B. <talli...@mitre.org> wrote: > > dtSearch allows a user to have NOTs embedded in proximity searches. > > And, if you're heading down the path of building your own queryparser to > handle dtSearch's syntax, please read and heed Charlie Hull's post: > > http://www.flax.co.uk/blog/2016/05/13/old-new-query-parser/ > > See also: > > > http://www.flax.co.uk/blog/2012/04/24/dtsolr-an-open-source-replacement-for-the-dtsearch-closed-source-search-engine/ > >
