Search finds a person by name and employer in one query - #2268
Merged
Merged
Conversation
„lukas siemens“ fand bisher niemanden, weil der ganze Text im Arbeitgeber stehen musste; jetzt muss eine Lebenslauf-Station die Wörter tragen, die nicht im Vor- oder Nachnamen stehen, in beliebiger Reihenfolge. Die Wörter einer Firma müssen in derselben Station stehen, damit „deutsche bank“ niemanden von der Telekom und einer anderen Bank findet, und kurze Wörter filtern als ganzes Wort („tu münchen“), ohne den Index zu treiben. Diesen Text hat ein KI-Agent in meinem Namen geschrieben. Ich weiß, dass das problematisch ist.
wintermeyer
added a commit
that referenced
this pull request
Sep 21, 2026
„müller siemens“ findet seit #2268 den Namen beim Arbeitgeber, aber die Hilfe verriet das nicht, und ähnlich klingende Namen fielen dabei weg. Mit „müller firma:siemens“ bleibt der Freitext eine Namenssuche samt Phonetik, der Operator filtert über dieselben Index-Arme wie die Lebenslaufsuche, und jede Zeile nennt die Station bei diesem Arbeitgeber. Kurze Werte gelten als ganzes Wort, damit „schule:tu“ die TU findet und nicht Stuttgart; gespeicherte Suchen und ihre Mails kennen beide Operatoren. Diesen Text hat ein KI-Agent in meinem Namen geschrieben. Ich weiß, dass das problematisch ist.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On
/search, "siemens" found everybody with Siemens in their CV, but "lukas siemens" found nobody: the whole text had to stand in one employer name.Now one CV entry has to hold the words the member's first or last name does not, in either order, so "lukas siemens" finds Lukas who worked at Siemens. The words of an employer have to stand in the same entry, so "deutsche bank" no longer counts someone who was at Deutsche Telekom and later at another bank. Words under three letters only filter, and as whole words: "tu münchen" finds the TU, not the "tu" inside "Hauptverwaltung München".
The rule lives in
Vutuv.Search.cv_arms/1;matched_entries/3reads the same rule, so each row names the entry that matched. On the production copy "michael siemens" runs in about 1 ms, driven by the trigram indexes from #2267.An AI agent wrote this text in my name. I know that is problematic.