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

StreamingDataSourceBuilder and filtering keys and segments #41

Closed
js-commit opened this issue Nov 21, 2024 · 1 comment
Closed

StreamingDataSourceBuilder and filtering keys and segments #41

js-commit opened this issue Nov 21, 2024 · 1 comment
Labels

Comments

@js-commit
Copy link

Is your feature request related to a problem? Please describe.
Can you please provide an example on how to use the StreamingDataSourceBuilder filter? I've tried passing in a single flag ID, and I've noticed that the filtering does not work. Perhaps there is some syntax in how you properly use it, and it's not clear in any of the documentation.

Describe the solution you'd like

  • An example on how to properly use the filter query parameter.

Additional context
The idea behind using a filter is to ensure that the service only listens to changes that it really cares about and resource usage when there are many flags.

@louis-launchdarkly
Copy link

Hello @js-commit, thank you for asking - the way that payload filtering (a beta feature) works is by creating the filter in LaunchDarkly UI, and having the SDK refer to the filter key. It doesn't work by specifying a flag key.

The functionality was added to the SDK in version 6.1.0, which enabled the ability to pass the payload filter key to the data source builder: https://launchdarkly.github.io/java-server-sdk/com/launchdarkly/sdk/server/integrations/StreamingDataSourceBuilder.html#payloadFilter

Please reach out to your account representative or file a support ticket to sign up for the beta.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants