Opened 17 years ago

Closed 16 years ago

Last modified 9 years ago

#201 closed enhancement (fixed)

NEAR search with two OR subqueries should be supported

Reported by: Richard Boulton Owned by: Olly Betts
Priority: normal Milestone: 1.0.12
Component: Library API Version: SVN trunk
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Operating System: All

Description (last modified by Olly Betts)

In trunk this now throws UnimplementedError, but it really should be supported:

import xapian
a=xapian.Query('A')
b=xapian.Query('B')
c=xapian.Query(xapian.Query.OP_OR, a, b)
d=xapian.Query(xapian.Query.OP_NEAR, c, c)

Change History (9)

comment:1 by Richard Boulton, 17 years ago

Blocking: 120 added

Marking as for 1.0.x - would be nice to fix soon, but certainly shouldn't block a release.

comment:2 by Olly Betts, 17 years ago

Owner: changed from New Bugs to Olly Betts

Oh, I have a partially written patch for this somewhere...

comment:3 by Olly Betts, 17 years ago

Operating System: All
Status: newassigned

comment:5 by Richard Boulton, 17 years ago

Description: modified (diff)
Milestone: 1.1

comment:6 by Richard Boulton, 17 years ago

Blocking: 120 removed

(In #120) Remove the unfixed dependencies so we can close this bug - they're all marked for the 1.1.0 milestone.

comment:7 by Olly Betts, 16 years ago

Description: modified (diff)

Fix formatting of description.

We should at least fix the AssertionError here, and that should be easy to do so let's try to do it for 1.0.0.

I did work on a patch to implement NEAR and PHRASE over subqueries but I didn't fully finish it and I'm not sure where it is now.

comment:8 by Olly Betts, 16 years ago

Description: modified (diff)
Milestone: 1.1.01.1.1
Summary: Attempting to create a NEAR search with two OR nodes gives assertion errorNEAR search with two OR subqueries should be supported
Type: defectenhancement

(In comment:7 I meant 1.1.0 not 1.0.0, though this will likely be backported to 1.0.10 too).

The AssertionError issue is fixed in trunk by r11706, so retitling, milestoning, etc.

comment:9 by Olly Betts, 16 years ago

Milestone: 1.1.11.0.12

Fixed in trunk r12228.

Setting milestone:1.0.12

comment:10 by Olly Betts, 16 years ago

Resolution: fixed
Status: assignedclosed

Fixed for 1.0.12 in branches/1.0 r12258.

Note: See TracTickets for help on using tickets.