Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filtering in federated catalog query #132

Closed
mspiekermann opened this issue Sep 1, 2023 Discussed in #126 · 6 comments
Closed

Filtering in federated catalog query #132

mspiekermann opened this issue Sep 1, 2023 Discussed in #126 · 6 comments
Assignees
Labels
stale triage all new issues awaiting classification

Comments

@mspiekermann
Copy link

Bug Report

Describe the Bug

As discussed in our Q&A session, "criteria" sections seems to have no effect in the request payload if you want to apply a filter.

Discussed in #126

Originally posted by veronikasiska July 21, 2023
Hello Everyone,
I tried to get filtering working for the Federated Catalog, but the "criteria" sections seems to have no effect in the request payload. I also found this in the code:

    @Provider(isDefault = true)
    public FederatedCacheStore defaultCacheStore() {
        //todo: converts every criterion into a predicate that is always true. must be changed later!
        return new InMemoryFederatedCacheStore(criterion -> offer -> true, new LockManager(new ReentrantReadWriteLock()));
    }

Is it correct, that criteria are not implemented yet, and are only a placeholder in the API definition? 😮

Expected Behavior

Criteria should apply a filter to result set.

Observed Behavior

Result set includes all items and filter criteria are ignored.

@mspiekermann mspiekermann added the triage all new issues awaiting classification label Sep 1, 2023
@github-actions
Copy link

github-actions bot commented Sep 1, 2023

Thanks for your contribution 🔥 We will take a look asap 🚀

@github-actions
Copy link

This issue is stale because it has been open for 28 days with no activity.

1 similar comment
@github-actions
Copy link

This issue is stale because it has been open for 28 days with no activity.

@github-actions
Copy link

github-actions bot commented Oct 7, 2023

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 7, 2023
@wolf4ood wolf4ood reopened this Oct 7, 2023
@github-actions github-actions bot removed the stale label Oct 8, 2023
Copy link

github-actions bot commented Nov 5, 2023

This issue is stale because it has been open for 28 days with no activity.

@github-actions github-actions bot added the stale label Nov 5, 2023
Copy link

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale triage all new issues awaiting classification
Projects
None yet
Development

No branches or pull requests

2 participants