[jira] [Created] (IGNITE-4880) .NET: Rename Impl types

Pavel Tupitsyn created IGNITE-4880: -- Summary: .NET: Rename Impl types Key: IGNITE-4880 URL: https://issues.apache.org/jira/browse/IGNITE-4880 Project: Ignite Issue Type: Improvement

[GitHub] ignite pull request #1692: Ignite-4878

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1692 Ignite-4878 Replace conns collection with ConcurrentLinkedDeque to avoid possible concurrent modification exception You can merge this pull request into a Git repository by running: $ git

[GitHub] ignite pull request #1693: Ignite 4876

GitHub user kdudkov opened a pull request: https://github.com/apache/ignite/pull/1693 Ignite 4876 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4876 Alternatively you can review and apply these

Re: Adding ML to Ignite, IGNITE-4572

Thank you for your reply. I will be watching this thread. However, GSOC applications are due Monday. So, some suggestions for what to write on the proposal would be great, if pull request will be later than Monday. -- View this message in context:

Re: Getting Started with Apache Ignite - Part 1

Fantastic guidance, I'll register on IMC - thanks Denis. On Tue, Mar 28, 2017 at 4:22 PM Denis Magda wrote: > Dani, excellent job! > > *Prachi*, could you publish the article to DZone and update Ignite’s > blogging page? Since this will be a series of posts don’t add DZone

Re: Adding ML to Ignite, IGNITE-4572

Alper - we are very close to "pull request" our preliminary work into ignite 2.0 (finger crossed it will make it into it). Once we have it available in the main ignite 2.0 branch there will be plenty of interesting tasks to tackle. Stay tuned on this thread! -- View this message in context:

[jira] [Created] (IGNITE-4881) REPLICATED cache size is wrong after node left topology.

Andrew Mashenkov created IGNITE-4881: Summary: REPLICATED cache size is wrong after node left topology. Key: IGNITE-4881 URL: https://issues.apache.org/jira/browse/IGNITE-4881 Project: Ignite

putting entity into cache while commiting.Why!?

Hello, Igniters! I have one more question to you. Will appreciate any help. Consider cache with near , dht configured not null. When we start commit transaction , in method *org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal#enlistWriteEntry* we put newly created entry

Stable binary key representation

Guys, I stumbled across this ticket [1] and it seems to me that the whole approach of identity resolvers is error-prone. If a key contains some data that does not participate in equals() calculation, these fields may be as well moved to the value object. Even with binary objects, key mutation

[GitHub] ignite pull request #1665: IGNITE-4617: Added field-access methods for Binar...

Github user isapego closed the pull request at: https://github.com/apache/ignite/pull/1665 --- 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

Re: IGNITE-2766 Spring Cache Manager ReConnect Issue

Hi Rishi, I will review in next couple of days. -Val On Tue, Mar 28, 2017 at 8:24 PM, Rishi Yagnik wrote: > Hi Val, > > Committed changes on IGNITE-2786, would like you to review the > changes.Would you please review it ? > > Thanks, > > On Mon, Mar 27, 2017 at 6:11 PM,

Re: putting entity into cache while commiting.Why!?

Hello Aleksey, No, the enlisted entry won't be visible for other transactions. Dirty reads are not allowed in Ignite. Kind regards, Alex 29 марта 2017 г. 7:36 PM пользователь "ALEKSEY KUZNETSOV" < alkuznetsov...@gmail.com> написал: Hello, Igniters! I have one more question to you. Will

Re: Stable binary key representation

I’m not sure we can simply discontinue the identity resolvers that were originally created for DML. *Vovan*, *Alex Paschenko*, please chime in and provide your thoughts. Don’t want us to make such decisions in haste. Alex G., in any case, assuming that the resolvers are still in 2.0 is there

Re: Stable binary key representation

Alex, How do you suggest to replace the CacheKey class? It's internal for Hibernate and I'm not sure it's possible. -Val On Wed, Mar 29, 2017 at 11:09 AM, Denis Magda wrote: > I’m not sure we can simply discontinue the identity resolvers that were > originally created for

Re: Stable binary key representation

Guys, nothing is impossible if you know a bit about reflection in Java :) We had a look at the CacheKey class and it is easily replaceable. Sergi 2017-03-29 21:49 GMT+03:00 Dmitriy Setrakyan : > On Wed, Mar 29, 2017 at 11:43 AM, Valentin Kulichenko < >

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

Solution implemented in core-level and works with binary-marshaller. If you about the cache queries - it works with compressed data. 2017-03-29 21:42 GMT+03:00 Dmitriy Setrakyan : > On Wed, Mar 29, 2017 at 10:56 AM, Denis Magda wrote: > > > Hello

Re: Stable binary key representation

On Wed, Mar 29, 2017 at 11:43 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > "Hibernate key" is the CacheKey class I was referring to. It's provided by > Hibernate, not by user and not by us. So I'm not sure it's possible to > replace it. > If it is impossible to replace or

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

On Wed, Mar 29, 2017 at 10:56 AM, Denis Magda wrote: > Hello Vyacheslav, thanks for your efforts. > > Is there any special support for SQL? In the original discussion [1] > around this task the folks expressed several concerns about compression > usefulness w/o the ability to

Re: Stable binary key representation

"Hibernate key" is the CacheKey class I was referring to. It's provided by Hibernate, not by user and not by us. So I'm not sure it's possible to replace it. -Val On Wed, Mar 29, 2017 at 11:36 AM, Dmitriy Setrakyan wrote: > Alexey, > > Can you explain what is the

Re: Stable binary key representation

It looks like a good idea to drop identity resolvers for now and require stable binary representation for keys in 2.0. Later if it will be really needed we will be able to add them back. Sergi 2017-03-29 19:08 GMT+03:00 Alexey Goncharuk : > Guys, > > I stumbled

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

Hello Vyacheslav, thanks for your efforts. Is there any special support for SQL? In the original discussion [1] around this task the folks expressed several concerns about compression usefulness w/o the ability to execute SQL queries over compressed data. In general it makes sense to run the

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

On Wed, Mar 29, 2017 at 11:44 AM, Vyacheslav Daradur wrote: > Solution implemented in core-level and works with binary-marshaller. > > If you about the cache queries - it works with compressed data. > Vyacheslav, can you please explain how the cache queries work with the

Re: IGNITE-4188, savepoints with atomic cache?

Sorry, I get lost in tickets. Yes, IGNITE-2313 has to be completed in 2.0 if we want to makes this change. — Denis > On Mar 29, 2017, at 2:12 AM, Дмитрий Рябов wrote: > > Savepoints marked for 2.1, exceptions for 2.0. Do you want me to make > exceptions first? > >

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

Queries works with BinaryObjectImpl. 1. In the full compression mode - compressed bytes sequence - will be decompressed at initialization of BinaryObjectImpl. 2. With annotated fields compression - value of compressed fields will be decompress at deserializing on demand, for example when calls

Re: Making News page more visible

Thanks, Denis! I agree that an anchor would make sense. Also really like the idea to add the social icons to make sharing fast and easy. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Making-News-page-more-visible-tp15763p15927.html Sent from the Apache

[GitHub] ignite pull request #1617: ignite-4141 JDBC driver should always set withKee...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/1617 --- 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

Re: Remove CacheAtomicWriteOrderMode.CLOCK mode.

Maxim, Andrey G., Igniters, What if go further and remove CacheAtomicWriteOrderMode enum from the public API at all? I see no sense to keep it for the only one option left - PRIMARY. Any objections? — Denis > On Feb 27, 2017, at 8:09 AM, Kozlov Maxim wrote: > > Hi

Re: jdbc vs jdbc2 packages

Val, Igniters, I still believe the thin client has a right for living. It’s ideal for use cases when someone attempts to connect to Ignite from a tool or some sort of interface and query the data or update it in non transactional fashion. A TCP/IP address as a connection string to the cluster

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

> At which point does this step take place? Do we deserialize right when we > receive the object over the wire? When put it in cache, after marshalling. Covered by properly configured existing tests. [1][2][3] > Forgive me if I don't know the internals, but does this happen when SQL > queries

Re: Stable binary key representation

I'm not saying there is no alternative solution. But let's implement it and prove that it works first, and remove resolvers only after that. -Val On Wed, Mar 29, 2017 at 12:18 PM, Sergi Vladykin wrote: > Guys, nothing is impossible if you know a bit about reflection

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

On Wed, Mar 29, 2017 at 11:57 AM, Vyacheslav Daradur wrote: > Queries works with BinaryObjectImpl. > > 1. In the full compression mode - compressed bytes sequence - will be > decompressed at initialization of BinaryObjectImpl. > At which point does this step take place? Do

[jira] [Created] (IGNITE-4879) System pool starvation while partition evicting.

Andrew Mashenkov created IGNITE-4879: Summary: System pool starvation while partition evicting. Key: IGNITE-4879 URL: https://issues.apache.org/jira/browse/IGNITE-4879 Project: Ignite

[GitHub] ignite pull request #1689: IGNITE-4847

Github user endian675 closed the pull request at: https://github.com/apache/ignite/pull/1689 --- 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

Re: Making News page more visible

Prachi, as one of the site maintainers, would you mind contributing this? Denis On Wednesday, March 29, 2017, Tom Diederich wrote: > Thanks, Denis! I agree that an anchor would make sense. Also really like > the > idea to add the social icons to make sharing fast

Re: ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

Sergi, Vovan, As SQL and binary marshaller maintainers could you plan to review the contribution? — Denis > On Mar 29, 2017, at 4:44 PM, Vyacheslav Daradur wrote: > >> At which point does this step take place? Do we deserialize right when we >> receive the object over

IGNITE-4052 ready for review

Hello everybody! Nikolay, the properties for mesos role and JUnit test were added. Review please the pull request - https://github.com/apache/ignite/pull/1662 Vadim Opolski 2017-03-24 18:41 GMT+03:00 Nikolai Tikhonov : > Great! Looking forward to the contribution. > > On

ignite-3592 is ready fo review (Provide some kind of pluggable compression SPI support)

Hello everyone. https://issues.apache.org/jira/browse/IGNITE-3592 is ready for review. ci.tests [1] look good. Upsource review was created.[2] Solution provides 2 way to use compression. 1. Full compression mode. Switches in the IgniteConfiguration#fullCompressionMode field. Full compression

[GitHub] ignite pull request #1690: Ignite 1.8.5

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1690 Ignite 1.8.5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.8.5 Alternatively you can review and apply

Re: IGNITE-4188, savepoints with atomic cache?

Finish savepoints or flag for atomic operations? Not sure about savepoints. Exceptions - yes. https://issues.apache.org/jira/browse/IGNITE-2313 isn't it? 2017-03-29 2:12 GMT+03:00 Denis Magda : > If we want to make the exception based approach the default one then the > task

Re: distributed transaction of non-single coordinator

Hi! No, i dont have ticket for this. In the ticket i have implemented methods that change transaction status to STOP, thus letting it to commit transaction in another thread. In another thread you r going to restart transaction in order to commit it. The mechanism behind it is obvious : we change

[GitHub] ignite pull request #1689: IGNITE-4847

GitHub user endian675 opened a pull request: https://github.com/apache/ignite/pull/1689 IGNITE-4847 ignite-4847 log4j2 2.8.1 upgrade You can merge this pull request into a Git repository by running: $ git pull https://github.com/endian675/ignite ignite-4847-1 Alternatively

Re: IGNITE-4052 ready for review

Thank you for your contribution! Please, don't forget to move ticket in "path available" state. On Wed, Mar 29, 2017 at 10:46 AM, Вадим Опольский wrote: > Hello everybody! > > Nikolay, the properties for mesos role and JUnit test were added. > > Review please the pull

[GitHub] ignite pull request #1691: Ignite 4284 1.8.5

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/1691 Ignite 4284 1.8.5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4284-1.8.5 Alternatively you can review

serializable tx prepare future

Hi all ! In GridNearTxLocal while preparing phase in optimistic mode : *org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal#prepareNearTxLocal* we check serializable() and create GridNearOptimisticSerializableTxPrepareFuture What is the point of serializable future ? --

Re: [GridCachePartitionExchangeManager] Pending transaction deadlock detection futures

Val, >> Does anyone have an idea why client mode in Visor affects behavior? I thought we already forced client mode there, no? Visor CMD was NOT reworked to client mode. So Visor CMD starts server node in daemon mode. On Wed, Mar 29, 2017 at 2:28 AM, Valentin Kulichenko <

Re: IGNITE-4188, savepoints with atomic cache?

Savepoints marked for 2.1, exceptions for 2.0. Do you want me to make exceptions first? 2017-03-29 11:24 GMT+03:00 Дмитрий Рябов : > Finish savepoints or flag for atomic operations? > Not sure about savepoints. Exceptions - yes. https://issues.apache. >

[jira] [Created] (IGNITE-4876) Tests: node stop should wait for cluster to see actual topology version

Alexey Goncharuk created IGNITE-4876: Summary: Tests: node stop should wait for cluster to see actual topology version Key: IGNITE-4876 URL: https://issues.apache.org/jira/browse/IGNITE-4876

[jira] [Created] (IGNITE-4877) Add test covers get(key, type) in direct way (via SpringCache)

Vyacheslav Daradur created IGNITE-4877: -- Summary: Add test covers get(key, type) in direct way (via SpringCache) Key: IGNITE-4877 URL: https://issues.apache.org/jira/browse/IGNITE-4877 Project:

[jira] [Created] (IGNITE-4878) IgniteH2Indexing can throw java.util.ConcurrentModificationException

Michael Griggs created IGNITE-4878: -- Summary: IgniteH2Indexing can throw java.util.ConcurrentModificationException Key: IGNITE-4878 URL: https://issues.apache.org/jira/browse/IGNITE-4878 Project: