Ticket #350 (assigned enhancement)

Opened 18 months ago

Last modified 14 months ago

Stopping wildcard expansion at some point

Reported by: asjo Owned by: olly
Priority: normal Milestone: 1.2.x
Component: QueryParser Version:
Severity: normal Keywords:
Cc: Blocked By:
Operating System: All Blocking:

Description (last modified by olly) (diff)

If there are many (many) terms with the same prefix and a wildcard search matching those is performed, the QueryParser tries to create a huge query, exhausting RAM even on reasonably sized machines (8GB).

Attached is a patch that makes it possible to ask the QueryParser to throw an exception if a wildcard expands to more than a configurable number of terms.

Some discussion on the mailinglist:

Attachments

0001-Add-set_max_wildcard_expansion-method-to-the-queryp2.patch Download (4.1 KB) - added by asjo 18 months ago.
Patch to add set_max_wildcard_expansion() to the QueryParser?

Change History

Changed 18 months ago by asjo

Patch to add set_max_wildcard_expansion() to the QueryParser?

Changed 18 months ago by olly

  • status changed from new to assigned
  • description modified (diff)
  • milestone set to 1.1.1

Adding to the 1.1.1 bucket...

Changed 17 months ago by olly

  • milestone changed from 1.1.1 to 1.1.4

Triaging milestone:1.1.1 bugs.

Changed 14 months ago by olly

  • milestone changed from 1.1.4 to 1.2.0

API addition, so punting to 1.2.x.

Note: See TracTickets for help on using tickets.