Timeline for finding keywords in text using full text search in PostgreSQL
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 22, 2017 at 21:20 | comment | added | Evan Carroll | @RobShepherd yea, it's just not possible. Nor do I see it happening anytime. It would be massively memory intensive. Now if your question is how do you make it happen. That's a much more complex question. It would involve building your own system with NLP. | |
| Jul 22, 2017 at 19:12 | comment | added | Rob Shepherd |
Actually I don't want jump, jumped, jumping to be distinct keywords - this was Evan's pedagogical example. I actually want jump and other way more distinct terms to be keywords, but to match jump, jumped, jumping. my non-specific requirement is to output just jump as the keyword that was found, even if it was a derivative/synonym/plural etc. I am trying to retrospectively 'tag' documents with some very specific criteria.
|
|
| Jul 21, 2017 at 21:36 | history | edited | joanolo | CC BY-SA 3.0 |
deleted 4 characters in body
|
| Jul 21, 2017 at 21:30 | comment | added | joanolo |
@EvanCarroll: (2) I know of (at least someof ) the disadvantages (maning I've never put it to use). But for this specific use case where the original poster wants jump, jumped, jumping to be distinct preset keywords, it seems to fit. (1) As per the plurals, you're right: dbfiddle here I'll update answer.
|
|
| Jul 21, 2017 at 21:23 | comment | added | Evan Carroll |
A few friendly notes: (1) simple doesn't actually take out plurals. (2) It actually presents a huge disadvantage in that stemming decreases selectivity. For instance, If you search for "houses" in "This is my house" with the simple dictionary it won't match, with the default it will. (3) it doesn't even take out stop words unless you create a dictionary from the template that does.
|
|
| Jul 21, 2017 at 18:49 | history | answered | joanolo | CC BY-SA 3.0 |