ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4439) Create attribute based node filter
Date Tue, 20 Dec 2016 23:24:58 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765550#comment-15765550

ASF GitHub Bot commented on IGNITE-4439:

GitHub user vkulichenko opened a pull request:


    IGNITE-4439 - Attribute based node filter


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vkulichenko/ignite ignite-4439

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1369
commit bc3da349d89d09aaf836a7de9d32edac7648c755
Author: Valentin Kulichenko <valentin.lulichenko@gmail.com>
Date:   2016-12-20T23:10:29Z

    IGNITE-4439 - Attribute based node filter


> Create attribute based node filter
> ----------------------------------
>                 Key: IGNITE-4439
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4439
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 1.8
>            Reporter: Valentin Kulichenko
>            Assignee: Valentin Kulichenko
>             Fix For: 1.9
> We have a {{CacheConfiguration.nodeFilter}} configuration property which takes a predicate
that defines on which nodes cache is deployed. Therefore using it implies creating a new class
and deploying it on all nodes.
> However, in vast majority of cases users filter out nodes based on custom attributes,
so it can be useful to provide such implementation out of the box.

This message was sent by Atlassian JIRA

View raw message