Skip to content

[ACC-2342] Add SearchFilter for FTS on content attributes#195

Draft
NotAPenguin0 wants to merge 4 commits intomainfrom
ACC-2342-round-two
Draft

[ACC-2342] Add SearchFilter for FTS on content attributes#195
NotAPenguin0 wants to merge 4 commits intomainfrom
ACC-2342-round-two

Conversation

@NotAPenguin0
Copy link
Contributor

Implemented by creating a hidden attribute on entities with a FTS filter on content where the text will be stored (by some other process in the AppServer/extraction engine).

@NotAPenguin0 NotAPenguin0 requested a review from a team as a code owner December 8, 2025 12:20
@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 8, 2025

Copy link
Contributor

@NielsCW NielsCW left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe you can already construct hidden attributes with the IgnoredFlag and eventually when you enable this search option in the console, scribe will generate the names, add the ignored flag and generate the sql indices. This appserver PR might be useful as a POC to try out some searches. But it is not required for searching content attributes.

@NotAPenguin0
Copy link
Contributor Author

I believe you can already construct hidden attributes with the IgnoredFlag and eventually when you enable this search option in the console, scribe will generate the names, add the ignored flag and generate the sql indices. This appserver PR might be useful as a POC to try out some searches. But it is not required for searching content attributes.

I'm not sure how this will work yet, since we also need some way to populate this extracted text attribute once the text extraction service is integrated, so I think the app server needs to know which attribute to place the extracted text in.

@thijslemmens
Copy link
Contributor

We should agree on a design before starting to implement.

@thijslemmens thijslemmens marked this pull request as draft December 9, 2025 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants