Vova, even though it operates on single key we will need to "pin" partition
so key does not go to another node.
Pavel, you can also send closures to all primary nodes to do local scan
query for each partition. This way you will go over each entry.
Thanks!
--
Yakov Zhdanov, Director R&D
*GridGain
Vasiliy Sisko created IGNITE-3217:
-
Summary: Text input in number field
Key: IGNITE-3217
URL: https://issues.apache.org/jira/browse/IGNITE-3217
Project: Ignite
Issue Type: Sub-task
Affinity run/call operate on a single key AFAIK.
On Mon, May 30, 2016 at 10:55 PM, Dmitriy Setrakyan
wrote:
> Actually I have seen a ticket to block moving partitions if affinityCall or
> affinityRun are called. I think once these tickets are implemented, the
> process will become reliable, no?
Actually I have seen a ticket to block moving partitions if affinityCall or
affinityRun are called. I think once these tickets are implemented, the
process will become reliable, no?
D.
On Mon, May 30, 2016 at 9:13 AM, Pavel Tupitsyn
wrote:
> Dmitriy, as I understand, there is no reliable way to
Valentin Kulichenko created IGNITE-3216:
---
Summary: Need to deduplicate addresses registered in the IP finder
Key: IGNITE-3216
URL: https://issues.apache.org/jira/browse/IGNITE-3216
Project: Ignit
Valentin Kulichenko created IGNITE-3215:
---
Summary: IgniteRDD should be able to work with BinaryObjects
Key: IGNITE-3215
URL: https://issues.apache.org/jira/browse/IGNITE-3215
Project: Ignite
Dmitriy, as I understand, there is no reliable way to do that if
rebalancing happens.
On Mon, May 30, 2016 at 6:50 PM, Dmitriy Setrakyan
wrote:
> I think we do support this use case. Why not send a computation to a server
> and then perform the iteration through the cache entries locally on that
Hi,
AFAIK, you cannot use 1.4.X version with Ignite.
If you want to use another version of H2 in your project,
you can try to use different classloader to load it separately.
Google it for details.
2016-05-30 9:20 GMT+03:00 王庆 :
> Hi，I am a developer from china .My English leaves much to be desi
I think we do support this use case. Why not send a computation to a server
and then perform the iteration through the cache entries locally on that
server?
On Mon, May 30, 2016 at 4:44 AM, Pavel Tupitsyn
wrote:
> Igniters,
>
> Looks like we do not have an efficient way to perform an action on E
Guys,
Can we release version 1.6 in Jira? Currently I can still assign tickets to
version 1.6, which is not correct.
D.
Hi，I am a developer from china .My English leaves much to be desired. Please
ingore these syntax errors.When I use the spatial index module in ignite1.6.0 ,
I found it depends 1.3.175 version of the H2, but I need to use the 1.4.X h2
version.
com.h2database
h2
1.3.175
co
GitHub user avinogradovgg opened a pull request:
https://github.com/apache/ignite/pull/764
Ignite 3183 to 7.6.1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-3183-to-7.6.1
Alternatively you can re
Nikolay Tikhonov created IGNITE-3214:
Summary: YARN allocates containers at random
Key: IGNITE-3214
URL: https://issues.apache.org/jira/browse/IGNITE-3214
Project: Ignite
Issue Type: Impr
Igniters,
Looks like we do not have an efficient way to perform an action on EVERY
cache entry.
Let's say I want to remove all entries that match a predicate.
My only option is to retrieve these entries via Scan or SQL query, and then
call removeAll.
This involves a lot of unnecessary network tri
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/763
Gridgain 7.5.24
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.24
Alternatively you can review and apply
Github user avinogradovgg closed the pull request at:
https://github.com/apache/ignite/pull/752
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Pavel Konstantinov created IGNITE-3213:
--
Summary: 'false' value in the caches list of cluster
Key: IGNITE-3213
URL: https://issues.apache.org/jira/browse/IGNITE-3213
Project: Ignite
Issu
Ksenia Rybakova created IGNITE-3212:
---
Summary: Servers get stuck with the warning "Failed to wait for
initial partition map exchange" during falover test
Key: IGNITE-3212
URL: https://issues.apache.org/jira/brow
Github user alpert closed the pull request at:
https://github.com/apache/ignite/pull/534
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user alpert closed the pull request at:
https://github.com/apache/ignite/pull/719
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Ksenia Rybakova created IGNITE-3211:
---
Summary: "Failed to reinitialize local partitions", "Failed to
wait for completion of partition map exchange" errors during failover test
Key: IGNITE-3211
URL: https://issue
Github user sboikov closed the pull request at:
https://github.com/apache/ignite/pull/729
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is ena
22 matches
Mail list logo
