https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42508

--- Comment #32 from Tomás Cohen Arazi (tcohen) <[email protected]> ---
I understand the concern about process, and I agree this would have benefited
from earlier discussion. I indeed read the previous attempt on this path which
was discussed on bug 17500. And I actually focused on the conclusions there for
the path I took.

To be clear, I don’t expect the existing patchset to be accepted just because
work has already gone into it. I submitted it because it represents the current
result of several iterations and gives us something concrete to evaluate: what
data needs to be indexed/materialized, where updates need to be triggered, and
what the replacement patron search path would look like.

I’m also not attached to Elasticsearch as the only possible backend. The same
indexing/materialization framework could support an SQL-backed denormalized
table, and I’m going to explore that next. If the consensus is that a DB-backed
search projection is a better fit for core, I’m happy to adapt the work in that
direction.

I agree we should avoid ending up with two parallel patron search systems that
Koha has to support forever. My goal is not to add another permanent code path,
but to identify a cleaner patron search architecture: ideally one search
interface, one update/materialization pipeline, and backend-specific drivers
only where needed. But beware there are outstanding issues around patron search
that are not just performance ones, but no fuzzy searching, no attribute
boosting, no typo tolerance, etc. All of those can be dramatically benefited
from searching in ES alone.

So maybe the useful next step is to discuss the desired architecture first:

* fix the current SQL queries/data structure directly;
* introduce a denormalized SQL search projection;
* make patron search pluggable;
* or support Elasticsearch as an optional backend.

The code I submitted is meant to inform that discussion, not bypass it.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to