Ticket #167 (closed Defect: worksforme)

Opened 13 years ago

Last modified 11 years ago

Text Search with wildcards

Reported by: JuergeN Owned by: jri
Priority: Major Milestone:
Component: DeepaMehta Standard Distribution Version: 4.0.6
Keywords: Cc:
Complexity: 3 Area:


I was just wondering, why I cannot use wildcards in the text search?

Change History

comment:1 Changed 13 years ago by jri

All in all you should be able to use wildcards.
The search string you enter is passed almost verbatim to Lucene.

1) DM always appends a trailing '*' to the search term to easify begin-of-word searches.
2) I just detected an (encoding) issue with '+' characters (for the moment use AND instead).

Example text: "Platform for collaboration and knowledge management"
All these search terms will have positive result:

plat* AND coll
coll* AND plat
plat* AND know*ge
super collab

Note: Lucene's default boolean operator is OR (instead of AND), thus the latter has a positive result (while "super AND collab" would not).

Perhaps you struggle at this IMPORTANT one: you can't search across different fields of a composed topic.
Example: a DM Note with Title "DeepaMehta" and Text "Software" can't be found by "DeepaMehta AND Software" (because the 2 terms appear in different fields).
Background: subject of Lucene indexing is a *single* topic (more precisely: subject of indexing as provided by the Neo4j Lucene component is a *single* Neo4j Node). On the contrary, as you know, a DM Note is a composite of *two* separate Topics.

Cross-field queries would require a more elaborate query processing resp. indexing at DM's side.

Does this answer you question? (there are some more search related aspects not mentioned here.)
What are the search terms you struggled with?

comment:2 Changed 12 years ago by jri

Does it work for you?

comment:3 Changed 11 years ago by jri

Is this still an issue?
You can use wildcards. See also #302.

comment:4 Changed 11 years ago by JuergeN

  • Status changed from new to closed
  • Resolution set to worksforme
Note: See TracTickets for help on using tickets.