Re: Apache Flink Sink + Ignite: Ouch! Argument is invalid

Hi Saikat, The results flink calculated before sending to sink is correct, but the results in Ignite is not correct. You can remove the sink and print the stream content to validate my point. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Quick question on data and index pages

Hi, 1. What are direct and indirect count in data page header used for? What is the difference? [ https://cwiki-test.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood#IgniteDurableMemory-underthehood-Freelists ] 2. Are data pages organized in a B+ tree structure or inde

Re: Thin Client lib: Python

Hi Prachi! At the moment I already have my documents (temporarily) published at RTD. This is how they look like at a whole: https://apache-ignite-binary-protocol-client.readthedocs.io/ I already have a separate section on examples: https://apache-ignite-binary-protocol-client.readthedocs.io/

Re: Thin Client lib: Python

Either ``` conn = Connection('example.com', 10800) cache_put(conn, cache_id('my-cache'), 'a', 1) ``` or ``` conn = Connection('example.com', 10800) my_cache_id = cache_id('my-cache') cache_put(conn, my_cache_id, 'a', 1) ``` It is also possible to give parameters names, if you like to. ``` con

Quick questions on B+ Trees and Partitions

Hi, 1. B+ tree initialization, BPlusTree.initTree, seems to be called for every partition. Why? https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/tree/BPlusTree.java 2. The documentation here, https://ap

Adding experimental support for Intel Optane DC Persistent Memory

Hi, I have added a new proposal to support Intel Optane DC Persistent Memory for Ignite here: https://cwiki.apache.org/confluence/display/IGNITE/Adding+Experimental+Support+for+Intel+Optane+DC+Persistent+Memory. I'm looking forward to your feedback and collaboration on this. Thanks, Mulugeta

Re: Dirty Reads and READ_COMMITTED

Let's suppose that some transaction is trying to update values A and B: *tx.start() * > *cache.put("A", 1);cache.put("B", 2); * *tx. commit();* If you use READ_COMMITTED isolation level, it is possible that you will read the new value of A and the old value of B. If you need to make sure

Re: Dirty Reads and READ_COMMITTED

I believe Ignite updates values during the commit phase, so it's not possible to get a dirty read even if you do not acquire distributed locks on reads with READ_COMMITTED isolation. But I would let other community members who are more knowledgeable in this topic to add there comments, as it's poss

Re: Thin Client lib: Python

Also I remember there are no hashcodes for NodeJS clients On Wed, Jul 25, 2018 at 10:46 PM, Dmitriy Setrakyan wrote: > I am still confused. Let's work through an example. Suppose I have a cache > named "my_cache" and I want to put an entry with key "a" and value "1". > > In Java, this code will

Re: Thin Client lib: Python

Hi Dmitry M, I am resposible for managing the Ignite documentation. At some point we will merge the python documentation on github into the main Ignite documentation. Currently, I am trying to restructure our thin client documentation in a way that it (thin client documentation) is consistent for

[jira] [Created] (IGNITE-9084) Trash in WAL after node stop may affect WAL rebalance

Pavel Kovalenko created IGNITE-9084: --- Summary: Trash in WAL after node stop may affect WAL rebalance Key: IGNITE-9084 URL: https://issues.apache.org/jira/browse/IGNITE-9084 Project: Ignite

Re: Thin Client lib: Python

I am still confused. Let's work through an example. Suppose I have a cache named "my_cache" and I want to put an entry with key "a" and value "1". In Java, this code will look like this: > *IgniteCache<...> myCache = ignite.cache("my-cache");myCache.put("a", 1);* How will the same code look in

Re: Deprecating LOCAL cache

Vladimir, Are you suggesting that a user cannot span more than one local cache in a cross cache LOCAL transactions. This is extremely surprising to me, as it would require almost no effort to support it. As far as mixing the local caches with distributed caches, then I agree, cross-cache transacti

[GitHub] ignite pull request #4433: IGNITE-9083 Compute (Affinity Run) TC configurati...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/4433 IGNITE-9083 Compute (Affinity Run) TC configuration timeouts because … …of infinite socket operation You can merge this pull request into a Git repository by running: $ git pull https://

[jira] [Created] (IGNITE-9083) Compute (Affinity Run) TC configuration timeouts because of infinite socket operation

Eduard Shangareev created IGNITE-9083: - Summary: Compute (Affinity Run) TC configuration timeouts because of infinite socket operation Key: IGNITE-9083 URL: https://issues.apache.org/jira/browse/IGNITE-9083

Re: Service grid redesign

Denis, long service initialization isn't a big problem for us. The problem is hung initialization, that means the service deployment will never complete. On Wed, Jul 25, 2018 at 8:08 PM Denis Mekhanikov wrote: > > Vyacheslav, > > I think, that this timeout shouldn't be mandatory, and it should be

Re: Dirty Reads and READ_COMMITTED

And no. I'm not describing REPEATABLE_READ. I'm describing https://en.wikipedia.org/wiki/Isolation_(database_systems)#Dirty_reads and how READ_COMMITTED isolation can avoid dirty reads. On Wed, Jul 25, 2018 at 11:20 AM, John Wilson wrote: > I agree with your description. But the documentation h

Re: Dirty Reads and READ_COMMITTED

I agree with your description. But the documentation https://apacheignite. readme.io/docs/transactions is misleading in stating that no read locks are acquired (says "READ_COMMITTED - Data is read without a lock and is never cached in the transaction itself."). Which should be wrong. Read locks ar

Re: [Question] Where could I find the ignite website template?

Hi Wu, I don't see any obstacles why you can't reuse our design. In general, we don't have any specific template. Our site is a set of custom CSS and HTML files stored here: https://svn.apache.org/repos/asf/ignite/site/trunk Feel free to reach out to Prachi (copied) who helps us a lot with the

Re: [MTCGA]: new failures in builds [1532575] needs to be handled

I'll take a look at this test as I'm an author of it. On Wed, Jul 25, 2018 at 6:56 PM wrote: > Hi Ignite Developer, > > I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. > I hope you can help. > > *New test failure in master > IgniteCacheClientReconnectTest.testClien

Re: Dirty Reads and READ_COMMITTED

Hi John, Read committed isolation typically implies that lock on read is not held throughout the transaction lifecycle, i.e. released right after read is completed (in Ignite this just means that no lock is required at all). This semantic allows second read to get an updated value that was already

[GitHub] ignite pull request #4432: IGNITE-8920 Fix transaction hanging on exception ...

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4432 IGNITE-8920 Fix transaction hanging on exception during commit You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-892

Dirty Reads and READ_COMMITTED

Hi, Consider the following transaction where we read key 1 twice. try (Transaction tx = Ignition.ignite().transactions().txStart(PESSIMISTIC, READ_COMMITTED)) { cache.get(1); //... cache.get(1); tx.commit(); } According to the documentation here, https://apacheignite.readme.io/docs/transactions,

[jira] [Created] (IGNITE-9081) Allow not-active cluster read metastore

Eduard Shangareev created IGNITE-9081: - Summary: Allow not-active cluster read metastore Key: IGNITE-9081 URL: https://issues.apache.org/jira/browse/IGNITE-9081 Project: Ignite Issue Type

Re: Service grid redesign

Vyacheslav, I think, that this timeout shouldn't be mandatory, and it should be disabled by default. We should be ready for long service initialization. So, it shouldn't be done in any crucial threads like discovery or exchange. Denis ср, 25 июл. 2018 г. в 15:59, Vyacheslav Daradur : > FYI, I'v

[jira] [Created] (IGNITE-9082) Throwing checked exception during tx commit without node stopping leads to data corruption

Pavel Kovalenko created IGNITE-9082: --- Summary: Throwing checked exception during tx commit without node stopping leads to data corruption Key: IGNITE-9082 URL: https://issues.apache.org/jira/browse/IGNITE-9082

Re: Need review IGNITE-9050

Hi, Igniters, especially Native Persistence Experts, please step in. Tests are still running, so I suggest to avoid merge until we'll get run-all results. Sincerely, Dmitriy Pavlov ср, 25 июл. 2018 г. в 16:24, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com>: > Igniters, > > I completed work

[jira] [Created] (IGNITE-9079) ODBC: Implement protocol version automatic downgrage for old servers

Igor Sapego created IGNITE-9079: --- Summary: ODBC: Implement protocol version automatic downgrage for old servers Key: IGNITE-9079 URL: https://issues.apache.org/jira/browse/IGNITE-9079 Project: Ignite

Re: ConcurrentLinkedHashMap works incorrectly after clear()

Hello! LT stops throttling input as soon as it is unable to add any entries to underlying map since it would consider itself full with 0 entries. I have tried to implement both suggestions, and they all have big impact on CLHM code. I am super uncomfortable with making non-trivial edits to it. I

[jira] [Created] (IGNITE-9078) Add documentation page with the list of ODBC versions

Igor Sapego created IGNITE-9078: --- Summary: Add documentation page with the list of ODBC versions Key: IGNITE-9078 URL: https://issues.apache.org/jira/browse/IGNITE-9078 Project: Ignite Issue Ty

RE: Deprecating LOCAL cache

In my view the approach in implementing LOCAL caches isn’t supposed to be highly efficient – just a functional workaround for the existing users of LOCAL cache. Moreover, if the workaround is easy but slightly awkward it isn’t a bad thing – a user needs to understand that their use case isn't di

[GitHub] ignite pull request #4431: IGNITE-9073 Use jackson2 dependency instead of ja...

GitHub user zzzadruga opened a pull request: https://github.com/apache/ignite/pull/4431 IGNITE-9073 Use jackson2 dependency instead of jackson1 You can merge this pull request into a Git repository by running: $ git pull https://github.com/zzzadruga/ignite IGNITE-9073 Alterna

Re: Thin Client lib: Python

Igor, That is a very good point. It just did not cross my mind during the implementation of this function, that the cache identifier can be abstract. I will fix that. On 07/26/2018 01:46 AM, Igor Sapego wrote: Well, at least name should be changed, IMO, as the API function name should say wh

Re: Deprecating LOCAL cache

Not sure that we can create cache with same name by different clients for this approach. On Wed, Jul 25, 2018 at 12:35 PM, Pavel Kovalenko wrote: > It's not easy to just make such caches as PARTITIONED with NodeFilter. > Even in the case when a node is not affinity node for this cache we create

[GitHub] ignite pull request #4430: IGNITE-9080 Activate | Deactivate Cluster is kill...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4430 ---

Re: Data regions on client nodes

Hi Maxim, thank you for stepping in. How do you think, is it possible to check cache assignment to region at stage of memory allocation? Sincerely, Dmitriy Pavlov ср, 25 июл. 2018 г. в 18:22, Maxim Muzafarov : > Folks, > > I've checked memory allocation. It looks like we are allocating memory o

[jira] [Created] (IGNITE-9080) Activate | Deactivate Cluster is killed by Linux OOM killer

Eduard Shangareev created IGNITE-9080: - Summary: Activate | Deactivate Cluster is killed by Linux OOM killer Key: IGNITE-9080 URL: https://issues.apache.org/jira/browse/IGNITE-9080 Project: Ignite

[MTCGA]: new failures in builds [1532575] needs to be handled

Hi Ignite Developer, I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I hope you can help. *New test failure in master IgniteCacheClientReconnectTest.testClientInForceServerModeStopsOnExchangeHistoryExhaustion https://ci.ignite.apache.org/project.html?projectId=I

Re: Thin Client lib: Python

Well, at least name should be changed, IMO, as the API function name should say what we do, and not how we do it. For example, cache_id() looks better to me than hashcode(). Best Regards, Igor On Wed, Jul 25, 2018 at 6:22 PM Dmitry Melnichuk < dmitry.melnic...@nobitlost.com> wrote: > Dmitriy, >

[jira] [Created] (IGNITE-9077) Metastorage content examination to ensure binary compatibility

Sergey Chugunov created IGNITE-9077: --- Summary: Metastorage content examination to ensure binary compatibility Key: IGNITE-9077 URL: https://issues.apache.org/jira/browse/IGNITE-9077 Project: Ignite

[GitHub] ignite pull request #4430: IGNITE-9080 Activate | Deactivate Cluster is kill...

GitHub user EdShangGG opened a pull request: https://github.com/apache/ignite/pull/4430 IGNITE-9080 Activate | Deactivate Cluster is killed by Linux OOM killer You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignit

Re: Thin Client lib: Python

Dmitriy, The short answer is: Python client uses hash code (or any cache identifier) instead of Java Cache object, since such an abstraction is not necessary in Python. As for why (IMO) Cache object may be needed in Java, but not in Python − the main reason is the difference in typing system

Re: Data regions on client nodes

Folks, I've checked memory allocation. It looks like we are allocating memory only on the first exchange future init on local join occurs on node. Also, seems like we are allocating only the first chunk of memory (not the whole bunch) and it calculates as: Math.max((maxSize - startSize) / (SEG_CN

Re: Thin Client lib: Python

Igor, Thank you for your elaborated response. I think the examples you gave me are valid for statically-typed languages only. At least not for Python. If we add an extra parameter to key-value operation, we just add it to a given API function as a named argument (“keyword argument” or “kwarg”

[GitHub] ignite pull request #4392: IGNITE-9041 AssertionError in TcpCommunicationSpi

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4392 ---

Re: Deprecating LOCAL cache

Vladimir, do we have a ticket for cross-cache transactions with LOCAL cache? I can't find it. In my task I met this situation in tests and I want to fail such tests with link to this ticket. 2018-07-25 12:55 GMT+03:00 Vladimir Ozerov : > Dima, > > LOCAL cache adds very little value to the product

[GitHub] ignite pull request #4406: IGNITE-9036 change version jersey2 from 2.6.5 to ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4406 ---

[jira] [Created] (IGNITE-9076) Service Grid: Introduce timeout to interrupt long Service#init on deployment

Vyacheslav Daradur created IGNITE-9076: -- Summary: Service Grid: Introduce timeout to interrupt long Service#init on deployment Key: IGNITE-9076 URL: https://issues.apache.org/jira/browse/IGNITE-9076

[GitHub] ignite pull request #4427: IGNITE-8546 Permission denied while copying OPTIO...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4427 ---

Need review IGNITE-9050

Igniters, I completed work on IGNITE-9050 (WALIterator should throw an exception if iterator stopped in the WAL archive but not in WAL work). review link - CR-697

[GitHub] ignite pull request #4423: IGNITE-9069 Hadoop and IGFS TC configurations fai...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4423 ---

[jira] [Created] (IGNITE-9074) ODBC: Wrong error message on handshake failure

Igor Sapego created IGNITE-9074: --- Summary: ODBC: Wrong error message on handshake failure Key: IGNITE-9074 URL: https://issues.apache.org/jira/browse/IGNITE-9074 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3670: IGNITE-7823

Github user xtern closed the pull request at: https://github.com/apache/ignite/pull/3670 ---

Re: Deprecating LOCAL cache

Hello! I have never seen the usage of LOCAL cache so far, so I am for its deprecation. Regards, -- Ilya Kasnacheev 2018-07-25 12:55 GMT+03:00 Vladimir Ozerov : > Dima, > > LOCAL cache adds very little value to the product. It doesn't support > cross-cache transactions, consumes a lot of memor

[Question] Where could I find the ignite website template?

Hi ignite community I am PPMC member of Apache SkyWalking(Incubating). I am interested in your official website[1]. It is a very good design. May I use this as the template to build SkyWalking's new website[2]? And where could I find the template source codes? [1] https://ignite.apache.org/i

Re: Deprecating LOCAL cache

Hi Igniters, I've never seen the LOCAL cache in the user list for 1 year. I've tried to search in archives and found only that mention http://apache-ignite-users.70518.x6.nabble.com/LOCAL-cache-and-EntryProcessor-td7419.html in 2016. Who can provide any additional usage examples? My vote goes to

Re: Service grid redesign

FYI, I've filled the tickets: https://issues.apache.org/jira/browse/IGNITE-9075 https://issues.apache.org/jira/browse/IGNITE-9076 On Wed, Jul 25, 2018 at 12:54 PM Vyacheslav Daradur wrote: > > > I think such timeout should be determined on per-service level. Can we make > > it part of the service

[GitHub] ignite pull request #4320: IGNITE-8944 - TcpDiscoverySpi: set connection che...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4320 ---

[GitHub] ignite pull request #4429: IGNITE-9050 WALIterator should throw an exception...

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/4429 IGNITE-9050 WALIterator should throw an exception if iterator stopped in the WAL archive but not in WAL work You can merge this pull request into a Git repository by running: $ git

Re: Deprecating LOCAL cache

It's not easy to just make such caches as PARTITIONED with NodeFilter. Even in the case when a node is not affinity node for this cache we create entities like GridClientPartitionTopology for such caches on all nodes. These caches participate in the exchange, calculate affinity, etc. on all nodes.

RE: Deprecating LOCAL cache

Deprecating something doesn’t mean an immediate impact on users. By deprecating LOCAL caches we would be saying that this functionality has limited support, has issues and will be removed *eventually*. By the time of 3.0 we’ll have a better idea about how many users are affected as they will be n

Re: Deprecating LOCAL cache

Vladimir, do we have a ticket for cross-cache transactions with LOCAL cache? I can't find it. In my task I met this situation in tests and I want to fail such tests with link to this ticket. Also documentation in readme.io say nothing about cross-cache failures with LOCAL cache. ср, 25 июл. 2018 г

Re: Documenting Ignite

Hi Artem, Could you please check if you can edit now. Sincerely, Dmitriy Pavlov ср, 25 июл. 2018 г. в 14:03, Artem Budnikov : > Hi Dmitry, > > I've added a comment to the issue. > > My Confluence ID is a.budnikov. Could you please grant me permissions > required to edit pages. Thanks! > > > Art

Re: ConcurrentLinkedHashMap works incorrectly after clear()

Hello Ilya, Can you add more info about why and how LT for this test case prints log message twice? >From my point, maiking clear() method to throw UnsupportedOperationException is not right fix for flaky test issues. A brief search through CLHM led me to a thought that we just forgot to drop dow

Re: Documenting Ignite

Hi Dmitry, I've added a comment to the issue. My Confluence ID is a.budnikov. Could you please grant me permissions required to edit pages. Thanks! Artem On 24.07.2018 16:58, Dmitry Pavlov wrote: I've noticed now INFRA asks for feedback from us. Artem, will you provide feedback on done c

RE: Deprecating LOCAL cache

To me it also raises a question of having REPLICATED :) But that might seem too radical, so let’s decide on the LOCAL first. I don’t mind keeping LOCAL as an alias for PARTITIONED with a default node filter, but I don’t see much benefit in it. Why to have a shortcut for something used by 1% (or

[jira] [Created] (IGNITE-9075) Service Grid: Lifecycle of affinity deployed service should be reworked

Vyacheslav Daradur created IGNITE-9075: -- Summary: Service Grid: Lifecycle of affinity deployed service should be reworked Key: IGNITE-9075 URL: https://issues.apache.org/jira/browse/IGNITE-9075 P

[GitHub] ignite pull request #4428: IGNITE-9074: Fixed ODBC error message on handshak...

GitHub user isapego opened a pull request: https://github.com/apache/ignite/pull/4428 IGNITE-9074: Fixed ODBC error message on handshake failure You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9074

Re: Does Ignite Txs Protect against Phantom Reads?

Hi Val, Thanks, that answers my question. John. On Tue, Jul 24, 2018 at 5:13 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi John, > > Looks like pictures can't be attached directly. Try uploading it somewhere > and providing a link. > > However, since you're talking about

Re: Deprecating LOCAL cache

Dima, LOCAL cache adds very little value to the product. It doesn't support cross-cache transactions, consumes a lot of memory, much slower than any widely-used concurrent hash map. Let's go the same way as Java - mark LOCAL cache as "deprecated for removal", and then remove it in 3.0. On Wed, Ju

Re: Service grid redesign

> I think such timeout should be determined on per-service level. Can we make > it part of the service configuration, or pass it into deploy method? Agree, per ServiceConfiguration level is more flexible solution. > This is a great question. Will the service be able to continue operating > after

Re: Thin Client lib: Python

Dmitriy, To me it seems that procedural approach makes it harder to maintaine code and add new features. For example, imagine that we are adding new feature for a thin client, and now we need to pass one more cache parameter when doing any key-value operation, such as put. In your approach, you wi

Re: Deprecating LOCAL cache

+1 to make LOCAL as filtered PARTITIONED cache. I think it would be much easier and faster than fixing all bugs. 2018-07-25 11:51 GMT+03:00 Dmitriy Setrakyan : > I would stay away from deprecating such huge pieces as a whole LOCAL cache. > In retrospect, we should probably not even have LOCAL cac

Re: Service grid redesign

On Tue, Jul 24, 2018 at 9:14 PM, Vyacheslav Daradur wrote: > Igniters, please help me to clarify the following questions: > > 1). According to the issue [1] we should propagate services deployment > results to an initiator, that means we should wait for wor > Service#init method completion. > How

[jira] [Created] (IGNITE-9073) Module ignite-kubernetes should use jackson2 dependency rater then jackson1

Denis Garus created IGNITE-9073: --- Summary: Module ignite-kubernetes should use jackson2 dependency rater then jackson1 Key: IGNITE-9073 URL: https://issues.apache.org/jira/browse/IGNITE-9073 Project: Ig

Re: Thin Client lib: Python

Dmitriy, To be honest, I got a bit lost in such a big email. Can you tell us briefly - why do we not need the hash code on API in Java and we do need it in Python? D. On Wed, Jul 25, 2018 at 3:29 AM, Dmitry Melnichuk < dmitry.melnic...@nobitlost.com> wrote: > Hello, Dmitriy, Igor! > > Dmitriy,

Re: Deprecating LOCAL cache

I would stay away from deprecating such huge pieces as a whole LOCAL cache. In retrospect, we should probably not even have LOCAL caches, but now I am certain that it is used by many users. I would do one of the following, whichever one is easier: - Fix the issues found with LOCAL caches, incl

[GitHub] ignite pull request #4427: IGNITE-8546 Permission denied while copying OPTIO...

GitHub user gromtech opened a pull request: https://github.com/apache/ignite/pull/4427 IGNITE-8546 Permission denied while copying OPTION_LIBS on Openshift * Added permissions to copy optional libs, create work dir and execute entry point. * Changed run.sh: `cp libs/optional/$li

[GitHub] ignite pull request #4426: ignite-8689: SQL query execution may lead to Null...

GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/4426 ignite-8689: SQL query execution may lead to NullPointerException while node is stopped You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgai

Re: Deprecating LOCAL cache

It sounds like the main drawback of LOCAL cache is that it's implemented separately and therefore has to be maintained separately. If that's the only issue, why not keep LOCAL cache mode on public API, but implement it as a PARTITIONED cache with a node filter forcefully set? That's similar to what

Re: Deprecating LOCAL cache

Huge +1 from me. One more SO question about LOCAL caches - https://stackoverflow.com/questions/49051079/is-it-possible-to-perform-sql-query-with-distributed-join-over-a-local-cache-and "It is not possible to perform joins (both distributed an co-located) between LOCAL and PARTITIONED caches. Th

[GitHub] ignite pull request #4419: IGNITE-9063 Correct DataFrame Partition Ordering

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4419 ---

Deprecating LOCAL cache

Hi Igniters, I’d like to start a discussion about the deprecation of the LOCAL caches. LOCAL caches are an edge-case functionality I haven’t done any formal analysis, but from my experience LOCAL caches are needed very rarely, if ever. I think most usages of LOCAL caches I’ve seen were misuses:

[GitHub] ignite pull request #4425: IGNITE-8924: Parameter Grid

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/4425 IGNITE-8924: Parameter Grid You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8924 Alternatively you can review a

[GitHub] ignite pull request #4424: IGNITE-7700

GitHub user devozerov opened a pull request: https://github.com/apache/ignite/pull/4424 IGNITE-7700 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7700-plekhanov Alternatively you can review and ap