PR IGNITE-1178 fix for NPE in GridCacheProcessor.onKernalStop()

Plz, review my PR : https://github.com/apache/ignite/pull/1517 https://issues.apache.org/jira/browse/IGNITE-1178 -- *Best Regards,* *Kuznetsov Aleksey*

ignite analysis with jepsen

Hello Igniters, There is fresh doc about mongodb analysis with jepsen tool: https://jepsen.io/analyses/mongodb-3-4-0-rc3 Looks like mongo soon would be production ready database ) And what do you think about the same analysis for ignite? I have no deal with jepsen but has a lot of positive feed

Re: DML data streaming

On Wed, Feb 15, 2017 at 2:41 PM, Alexander Paschenko < alexander.a.pasche...@gmail.com> wrote: > Folks, > > Regarding INSERT semantics in JDBC DML streaming mode - I've left only > INSERTs supports as we'd agreed before. > > However, current architecture of streaming related internals does not >

Re: Inaccurate documentation about transactions

postgres has the different viewpoint, i hope. https://www.postgresql.org/docs/9.1/static/transaction-iso.html Read Committed Isolation Level Read Committed is the default isolation level in PostgreSQL. When a transaction uses this isolation level, a SELECT query (without a FOR UPDATE/SHARE

Re: DML data streaming

Folks, Regarding INSERT semantics in JDBC DML streaming mode - I've left only INSERTs supports as we'd agreed before. However, current architecture of streaming related internals does not give any clear way to intercept key duplicates and inform the user - say, I can't just throw an exception

error - Failed to wait for partition release future

Hi, I am getting the following error in Ignite version 1.8.1 : "Failed to wait for partition release future" The related logs lines are at the bottom. I was curious if it could be related to https://issues.apache.org/jira/browse/IGNITE-3212 which has fix for version 1.9. Could this be the

Re: DML data streaming

On Wed, Feb 15, 2017 at 4:28 AM, Vladimir Ozerov wrote: > Ok, let's put aside current fields configuration, I'll create separate > thread for it. As far as _KEY and _VAL, proposed change is exactly about > mappings: > > class QueryEntity { > ... > String

Re: Inaccurate documentation about transactions

This is even better. Alexandr, could you do this since you already know what’s transaction and what isn’t? — Denis > On Feb 15, 2017, at 10:50 AM, Dmitriy Setrakyan wrote: > > Why not just have @IgniteTransactional annotation and attach it to all the > transactional

Re: IGNITE-4534 - Ignite 2.0 eviction design

On Wed, Feb 15, 2017 at 9:06 AM, Alexey Goncharuk < alexey.goncha...@gmail.com> wrote: > Dmitriy, > > For the current off-heap approach, we only have a per-entry LRU eviction > policy which does not fit well page memory architecture. I like the > adaptation of clock pro algorithm because it

Is there a faster way to launch an ignite client ?

Hey, Launching an ignite client on the same machine as the ignite server, with the simplest configuration (VmIpFinder on localhost) through the java interface can take anywhere between 5 and 10 seconds. I'm refactoring an ignite based CLI utility and am focusing on improving its statup time. Any

Re: IGNITE-2741 - spring session design

Hi Rishi, Thanks, I'll take a look. -Val On Wed, Feb 15, 2017 at 9:07 AM, Rishi Yagnik wrote: > Hi Val, > > As promised, please find attached code for spring boot integration with > spring security along with Ignite. > > Some more information on project - > >- It is

Re: Inaccurate documentation about transactions

Why not just have @IgniteTransactional annotation and attach it to all the transactional methods? On Wed, Feb 15, 2017 at 9:48 AM, Denis Magda wrote: > Alexander, > > Thanks for extensive feedback. I do support your idea that we need to > specify explicitly which methods are

Re: Python Ignite client (Requires ignite-rest-http)

Hi Danny, Excellent news, thanks for sharing! Cross-posting to the dev list. By the way, don’t you want take part or take over the full-fledged Python lib development? https://issues.apache.org/jira/browse/IGNITE-4600 — Denis > On Feb 14,

Re: Is there a faster way to launch an ignite client ?

Hi Danny, Try to reduce the port range in your VmIpFinder. If the range is long and you’re on a Windows machine, then it can take time to iterate over every IP:port combination in condition that some of IP:ports are not presently used. — Denis > On Feb 15, 2017, at 9:12 AM, Danny Shemesh

Re: Inaccurate documentation about transactions

Alexander, Thanks for extensive feedback. I do support your idea that we need to specify explicitly which methods are transactional and which aren’t. > Only after deep multi-thread testing, and consulting with other developers, I > get know that only get and put methods are running within

Re: Apache Ignite 1.9

Anton, The implementation is correct and was reviewed by Val long time ago. The only issue that is left is the compilation in *TeamCity* only. You fixed it for one scala version and now should simply do the same for other scala version by adding a new suite to TeamCity and adjusting the pom. —

Re: IGNITE-4534 - Ignite 2.0 eviction design

Dmitriy, For the current off-heap approach, we only have a per-entry LRU eviction policy which does not fit well page memory architecture. I like the adaptation of clock pro algorithm because it requires a significantly smaller amount of memory to track page updates and is scan-resistant. I want

[GitHub] ignite pull request #1539: IGNITE-1624 [not ready, just for testing]

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/1539 IGNITE-1624 [not ready, just for testing] Not ready. just for testing in CI. You can merge this pull request into a Git repository by running: $ git pull https://github.com/SharplEr/ignite

[jira] [Created] (IGNITE-4707) Add documentation for HA IGFS client

Vladimir Ozerov created IGNITE-4707: --- Summary: Add documentation for HA IGFS client Key: IGNITE-4707 URL: https://issues.apache.org/jira/browse/IGNITE-4707 Project: Ignite Issue Type: Task

[GitHub] ignite pull request #1538: Ignite-gg-11901 package renaming

GitHub user DmitriyGovorukhin opened a pull request: https://github.com/apache/ignite/pull/1538 Ignite-gg-11901 package renaming You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11901

Re: general question

hmm, why and how EvictionManager tracks an entry ? вт, 14 февр. 2017 г. в 23:07, Andrey Mashenkov : > Hi Aleksey, > > EvictableEntry.meta is used by EvictionManager to track entry. > Actually it may contains Node of EvictionPolicy queue to manupulate queue > items in

[GitHub] ignite pull request #1537: IGNITE-1948

GitHub user SharplEr opened a pull request: https://github.com/apache/ignite/pull/1537 IGNITE-1948 I divided ClusterTopologyCheckedException into two: ClusterTopologyCheckedException (with readyFut) and ClusterTopologyLocalException (without readyFut).

IGNITE-3422 - ready for review

Hello everyone. Please, review implemented solution. https://issues.apache.org/jira/browse/IGNITE-3422 - No way to control object initialization during deserialization/unmarshalling ci.tests

[GitHub] ignite pull request #1530: IGNITE-4693 Add possibility to wrap Java plugin e...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1530 --- 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: DML data streaming

Vladimir, Looks good to me. Pavel, No worries, it will work exactly like you described: hidden _key and _val fields will be always accessible. Sergi 2017-02-15 15:56 GMT+03:00 Pavel Tupitsyn : > I have no particular opinion on how we should handle _key/_val, > but we

Re: IGNITE-13

Hello everybody! Valentin, yes, I can create a micro benchmark and check if it gives any improvement. Vadim 2017-02-15 0:52 GMT+03:00 Valentin Kulichenko : > Vladimir, > > I think we misunderstood each other. My understanding of this optimization > is the

Re: DML data streaming

I have no particular opinion on how we should handle _key/_val, but we certainly need a way to select entire key and value objects via SqlFieldsQuery, and this should work without any additional configuration. We can rename these, turn them into system functions, whatever. Ignite.NET LINQ

[GitHub] ignite pull request #1524: IGNITE-4685 Propagate platform plugin configurati...

Github user ptupitsyn closed the pull request at: https://github.com/apache/ignite/pull/1524 --- 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: DML data streaming

Ok, let's put aside current fields configuration, I'll create separate thread for it. As far as _KEY and _VAL, proposed change is exactly about mappings: class QueryEntity { ... String keyFieldName; String valFieldName; ... } The key thing is that we will not require users to be

Re: DML data streaming

I don't see any improvement here. Usability will only suffer with this change. I'd suggest to just add mapping for system columns like _key, _val , _ver. Sergi 2017-02-15 13:18 GMT+03:00 Vladimir Ozerov : > I think the whole QueryEntity class require rework to allow for

IGNITE-602

Hello, can you answer me a simple question? We have 2 looping lists: ArrayList list1 = new ArrayList<>(); ArrayList list2 = new ArrayList<>(); list2.add(list1); list1.add(list2); Class GridToStringBuilder represent them into string. Simple public static String toString(Class cls, T obj)

[jira] [Created] (IGNITE-4706) Rewrite test GridTaskExecutionSelfTest::testJobIdCollision to use multiple JVMs

Sergey Chugunov created IGNITE-4706: --- Summary: Rewrite test GridTaskExecutionSelfTest::testJobIdCollision to use multiple JVMs Key: IGNITE-4706 URL: https://issues.apache.org/jira/browse/IGNITE-4706

[jira] [Created] (IGNITE-4705) Atomic cache protocol change: notify client node from backups

Semen Boikov created IGNITE-4705: Summary: Atomic cache protocol change: notify client node from backups Key: IGNITE-4705 URL: https://issues.apache.org/jira/browse/IGNITE-4705 Project: Ignite

[GitHub] ignite pull request #1535: IGNITE-4694 Add tests to check there are no memor...

GitHub user gvvinblade opened a pull request: https://github.com/apache/ignite/pull/1535 IGNITE-4694 Add tests to check there are no memory leaks in PageMemory You can merge this pull request into a Git repository by running: $ git pull

Re: Questions of the Ignite Configurations

Vladimir, thanks for your answers. 2017-02-15 13:32 GMT+03:00 Vladimir Ozerov : > Hi Vyacheslav, > > Answering your questions: > > 1. Yes > 2. Yes > 3. Only binary infrastructure > 4. Yes > > On Wed, Feb 15, 2017 at 12:32 PM, Vyacheslav Daradur >

Re: Questions of the Ignite Configurations

Hi Vyacheslav, Answering your questions: 1. Yes 2. Yes 3. Only binary infrastructure 4. Yes On Wed, Feb 15, 2017 at 12:32 PM, Vyacheslav Daradur wrote: > Hello everybody. > > I have some questions about classes of configuration in the Ignite. > > 1. IgniteConfiguration -

Re: DML data streaming

I think the whole QueryEntity class require rework to allow for this change. I would start with creating QueryField class which will encapsulate all field properties which are currently set through different setters: class QueryField { String name; String type; String alias;

Re: Sort nodes in the ring in order to minimize the number of reconnections

Need to do code review until February 17, if we want to get this feature in version 1.9. 2017-02-08 22:14 GMT+03:00 Александр Меньшиков : > Done. Please look. > > JIRA: https://issues.apache.org/jira/browse/IGNITE-4501 > PR: https://github.com/apache/ignite/pull/1436/files

Questions of the Ignite Configurations

Hello everybody. I have some questions about classes of configuration in the Ignite. 1. IgniteConfiguration - is it only one instance per Ignite-node? 2. BinaryConfiguration - is it only one instance per Ignite-node? 3. Does BinaryConfiguration relates only to binary-infrastructure or I can

Re: Apache Ignite 1.9

Denis, I don't know what is the plan for this issue. You asked me to fix compilation and thats what I done :) , but I'm not sure that issue implemented in proper way. I don't like changes I've done, they looks redundant although it works. Do we have somebody more familiar with spark inside the

Re: Inaccurate documentation about transactions

Alexandr, If you PUT some value within transaction, this is absolutely normal that you will see it on successive GET in the _same_ transaction. DIRTY_READ is a different thing - it allows reads of not-yet-committed changes from _another_ transaction. On Wed, Feb 15, 2017 at 9:41 AM, Alexandr