This might be a topic for Ignite 3.0, but I do agree that the ability to
create custom node filters is unnecessary and error-prone. Attribute-based
filtering should be more than enough.
-Val
On Tue, Jul 14, 2020 at 3:15 AM Pavel Tupitsyn wrote:
> Alex,
>
> Thank you for diving into this.
>
Alex,
Thank you for diving into this.
Indeed, custom node filters seem to have some issues.
1. For .NET, I'm fairly certain that we don't need custom node filters.
Let's just make AttributeNodeFilter available natively (as a .NET class).
2. For Java, we should at least fix the "call filter on
Hi,
I'm working on adding the NodeFilter functionality to the .NET client
https://issues.apache.org/jira/browse/IGNITE-2890
And there are several points I want to highlight regarding the current
implementation:
1) A node filter is being called on every put which seems redundant. This
might be
