refresh relayFilter after relay changed #103
Open
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.
If a client is configed to pull data from multi relays and these relays has diffrent id-source relationship,the client' partition thread may pull all partition's data from relay.That's because the _relayFilter property can't be refreshed after client change relay. For example:
2.RA and RB conern one table T , but has diffrent id-source relation.RA's source config is:
id:1,
source:test.T
RB's source config is:
id:2,
source:test.T
4.client pull data from RA and the stream request's filter params looks like this:
{"1":{"partitionType":"MOD","filters":[{"bktRange":{"start":0,"end":1},"numBuckets":10}]}}