-
Notifications
You must be signed in to change notification settings - Fork 136
IGNITE-18953 Add the ability to set attributes for a node to use them for filtering specific nodes #1819
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
Conversation
...integrationTest/java/org/apache/ignite/internal/cluster/management/ItClusterManagerTest.java
Outdated
Show resolved
Hide resolved
...nt/src/main/java/org/apache/ignite/internal/cluster/management/topology/api/LogicalNode.java
Outdated
Show resolved
Hide resolved
...rationTest/java/org/apache/ignite/internal/cluster/management/raft/ItCmgRaftServiceTest.java
Outdated
Show resolved
Hide resolved
...ache/ignite/internal/cluster/management/configuration/NodeAttributesConfigurationSchema.java
Outdated
Show resolved
Hide resolved
...nt/src/main/java/org/apache/ignite/internal/cluster/management/topology/api/LogicalNode.java
Outdated
Show resolved
Hide resolved
| /** | ||
| * Constructor. | ||
| * | ||
| * @param clusterNode Represents a node in a cluster.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's either "..." or '.')) And yep both clusterNode and LogicalNode represents a node in a cluster. We should either remove meaningless javadoc or add more definitions, e.g. saying that it's not a cluster, put network topology etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
e.g. saying that it's not a cluster, put network topology etc.
To be honest, I didn't understand your comment fully, could you please elaborate a bit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two points after the "cluster". Minor, won't wait for it. Please fix somewhere aside.
...c/test/java/org/apache/ignite/internal/distributionzones/util/DistributionZonesTestUtil.java
Outdated
Show resolved
Hide resolved
...c/test/java/org/apache/ignite/internal/distributionzones/util/DistributionZonesTestUtil.java
Outdated
Show resolved
Hide resolved
...unner/src/integrationTest/java/org/apache/ignite/internal/compute/ItLogicalTopologyTest.java
Show resolved
Hide resolved
… filtering specific nodes added (apache#1819)
* Add `source.offset.mode` property * `NONE` - do not store CQ watermark in Kafka - no resume on restart * `ALL` - store CQ watermark with every Kafka source record - resume CQ on connector restart * Add `source.offset.fail.mode` property * `FAIL` - fails CQ when stored watermark is too old * `IGNORE` - ignores invalid watermark and starts the connector anyway, potentially missing some updates Additionally: * Add `CONTINUOUS_QUERY_ERR_GROUP` and `WATERMARK_TOO_OLD_ERR` to handle watermark errors by code * Optimize watermark serialization with `watermarkBytes` and `fromBytes` to avoid extra array allocation
https://issues.apache.org/jira/browse/IGNITE-18953