[jira] [Created] (IGNITE-4667) Throw exception on starting client cache when indexed types cannot be loaded

Dmitry Karachentsev created IGNITE-4667: --- Summary: Throw exception on starting client cache when indexed types cannot be loaded Key: IGNITE-4667 URL: https://issues.apache.org/jira/browse/IGNITE-4667

Re: Test failures

How could they co-exist ? When you developing some ticket you are risking introduce bug which is reproduced by already failed test(s). Moreover its time consuming to look up new failed tests when your build has completed. The last one, committers who introduced new bugs is responsible for them and

[jira] [Created] (IGNITE-4666) Web console: Refactor clone dialog service to custom input service

Vasiliy Sisko created IGNITE-4666: - Summary: Web console: Refactor clone dialog service to custom input service Key: IGNITE-4666 URL: https://issues.apache.org/jira/browse/IGNITE-4666 Project: Ignite

Re: Ignite-2.0 - Make near readers update async by default

Filed a ticket https://issues.apache.org/jira/browse/IGNITE-4665 --Yakov 2017-02-07 0:49 GMT+07:00 Dmitriy Setrakyan : > On Mon, Feb 6, 2017 at 12:29 AM, Yakov Zhdanov > wrote: > > > What users do not expect is that partitioned cache suddenly turns

[jira] [Created] (IGNITE-4665) Make near readers update async by default

Yakov Zhdanov created IGNITE-4665: - Summary: Make near readers update async by default Key: IGNITE-4665 URL: https://issues.apache.org/jira/browse/IGNITE-4665 Project: Ignite Issue Type:

Re: jdbc vs jdbc2 packages

"undeprecating" - lol :D Consider introducing @Un annotation which negates all annotations on the same level and below. I would probably agree with Val and Vova, but adding features to thin-client seems questionable to me. Is these possible: 1. avoid dependencies on client machine and require

Re: Transaction semantics questions

Val, I think value read which is about to be overwritten by a commit is possible. I think only pessimistic repeatable read tx can protect you against that. Also, it seems there are no difference between read from one node and read from several nodes here. In primary_sync mode primaries send

Transaction semantics questions

Folks, I've got couple of questions about transactional behavior in Ignite that I want to clarify. 1. With READ_COMMITTED isolation, do I have atomicity guarantee when reading multiple values? For example, first transaction commits keys [1,2,3,4,5], while another does getAll([2,4]). Is it

Re: Ensure that builder approach is used for all setters in public API

+1 to Vladimir suggestion --Yakov 2017-02-07 20:50 GMT+07:00 Vladimir Ozerov : > Andrey, Valya, > > There is another problem here. What is we decide to add some existing > setter method to MBean? If it has signature "T setSomething(...)", we will > not be able to do so. We

[GitHub] ignite pull request #1504: 11737 : Rebalancing removes in persistence mode.

GitHub user ilantukh opened a pull request: https://github.com/apache/ignite/pull/1504 11737 : Rebalancing removes in persistence mode. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-11737

Re: Ensure that builder approach is used for all setters in public API

Vova, You mean that MBean implementation will encapsulate the corresponding SPI and delegate to its getters and setters as needed? If so, I like it, sounds like a very clean and flexible approach. -Val On Tue, Feb 7, 2017 at 5:50 AM, Vladimir Ozerov wrote: > Andrey,

Re: Swap Space for Caches

Hi Kevin, This is not a brand new discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Global-off-heap-memory-limit-td11267.html Basically, global limit could be useful, but we decided not to do that because 2.0 will completely change the configuration anyway. -Val On Tue, Feb 7,

Swap Space for Caches

We are encountering a limitation with Ignite Cache and swapping to disk, the issue that we are running into is that for some collections we need this tier of caching. on_heap -> off_heap -> swap to disk. The issue is that to get the swap to disk, we have to set a maximum off heap size for each

[GitHub] ignite pull request #1503: Ignite yyyy

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

Re: IGNITE-3196 - ready for review

+ Vladimir Ozerov It would be better if Vladimir Ozerov does the final review considering all the changes in .NET, C++ and Java. Vladimir, could you do that? — Denis > On Feb 7, 2017, at 5:04 AM, Vyacheslav Daradur wrote: > > +Denis > > >>Ok, so we agree on .NET and

Re: Test failures

Aleksey, Bugs fixing and features development are two processes that usually co-exist. Some of the committer/contributors fix tests/functionality while the others add new functionality. Someone does both. You’re welcomed to start fixing the failing tests. Are there any specific that annoys

Re: IGNITE-4374 - Ignite should validate JVM and OS configuration and output warning in log

Thanks, reviewed. — Denis > On Feb 7, 2017, at 3:58 AM, Vyacheslav Daradur wrote: > > Hi, I changed the output. > > Please, review it again) > > If something is bad, I will quickly correct. > > Thanks. > > 2017-01-25 18:24 GMT+03:00 Vyacheslav Daradur

Test failures

We have a lot of failed tests, which is frustrating. Some of them are flaky(floating status randomly goes from succesful to failed) which adds to frustration. Perhaps, we should fix all the tests in first place, and then continue doing tickets ? -- *Best Regards,* *Kuznetsov Aleksey*

Re: Contributing to Ignite.NET

Sergey, good job! I've replied in the ticket. Pavel On Tue, Feb 7, 2017 at 6:20 PM, Guru Stron wrote: > Can you please review the changes in pull request #1502 > . > > Thank you. > > On 7 February 2017 at 18:18, Guru Stron

IGNITE-1178

will take https://issues.apache.org/jira/browse/IGNITE-1178 if you don't mind -- *Best Regards,* *Kuznetsov Aleksey*

Re: Contributing to Ignite.NET

Can you please review the changes in pull request #1502 . Thank you. On 7 February 2017 at 18:18, Guru Stron wrote: > Hi, > > I've finished developing the changes for the .NET: Support > "ICollection.Contains" in LINQ >

Re: Contributing to Ignite.NET

Hi, I've finished developing the changes for the .NET: Support "ICollection.Contains" in LINQ ticket. Local LINQ tests are passing, also I've triggered build on TC

Re: IGNITE-1948 ClusterTopologyCheckedException can return null for retryReadyFuture()

Alexey, I ran into some difficulties. Look at the method: GridNearTxFinishFuture.CheckBackupMiniFuture#onDhtFinishResponse(GridDhtTxFinishResponse res) *Throwable err* = res.checkCommittedError(); if (*err* != null) { if (*err* instanceof

[jira] [Created] (IGNITE-4664) Add lifecycle and injection support for TopologyValidator

Alexei Scherbakov created IGNITE-4664: - Summary: Add lifecycle and injection support for TopologyValidator Key: IGNITE-4664 URL: https://issues.apache.org/jira/browse/IGNITE-4664 Project: Ignite

Re: Ensure that builder approach is used for all setters in public API

Andrey, Valya, There is another problem here. What is we decide to add some existing setter method to MBean? If it has signature "T setSomething(...)", we will not be able to do so. We need to understand how to deal with it, so that possible further improvements to MBean-s are not compromised.

[GitHub] ignite pull request #1502: Feature/ignite 4425

GitHub user gurustron opened a pull request: https://github.com/apache/ignite/pull/1502 Feature/ignite 4425 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gurustron/ignite feature/IGNITE-4425 Alternatively you can review and

Re: Ensure that builder approach is used for all setters in public API

Val, void setBatchSize(int batchSize) void setMaxMemorySize(long maxMemSize) void setMaxSize(int max) void setExcludePaths(Collection excludePaths) void setMaxBlocks(int maxBlocks) void setParallelJobsNumber(int num) void setWaitingJobsNumber(int num)

Re: IGNITE-3244

I have a solution on this task, this is pull request into my forked repository : https://github.com/voipp/ignite/pull/6 пн, 6 февр. 2017 г. в 16:03, ALEKSEY KUZNETSOV : > Moreover, in CacheObjectBinaryProcessorImpl#marshalToBinary() we > explicitly marshal objects array

Re: IGNITE-3196 - ready for review

+Denis >>Ok, so we agree on .NET and C++ parts, only Java part is to be reviewed. >>Denis, can you have a look? 2017-02-07 15:27 GMT+03:00 Pavel Tupitsyn : > Ok, so we agree on .NET and C++ parts, only Java part is to be reviewed. > > Denis, can you have a look? > > Pavel

Re: IGNITE-3196 - ready for review

Ok, so we agree on .NET and C++ parts, only Java part is to be reviewed. Denis, can you have a look? Pavel On Tue, Feb 7, 2017 at 3:23 PM, Igor Sapego wrote: > Looks good to me. > > Best Regards, > Igor > > On Tue, Feb 7, 2017 at 2:55 PM, Vyacheslav Daradur

Re: IGNITE-3196 - ready for review

Looks good to me. Best Regards, Igor On Tue, Feb 7, 2017 at 2:55 PM, Vyacheslav Daradur wrote: > Ok, thanks for explanations. > > What about this task? > > 2017-02-07 13:57 GMT+03:00 Igor Sapego : > >> But that's Ok. Since we use int8_t for bytes in

Re: Rethink native SQL API in Apache Ignite 2.0

Keep in mind security, e.g. SQL injections. Ideally the API should be designed in such a way that the programmer cannot use it wrongly and allow sql injections. > On 7 Feb 2017, at 12:34, Vladimir Ozerov wrote: > > Igniters, > > Our SQL engine becomes more and more

Re: IGNITE-4374 - Ignite should validate JVM and OS configuration and output warning in log

Hi, I changed the output. Please, review it again) If something is bad, I will quickly correct. Thanks. 2017-01-25 18:24 GMT+03:00 Vyacheslav Daradur : > GridPerformanceSuggestions isn't changed. > > JVM checks are encapsulated in JvmConfigurationSuggestions > OS checks

Re: IGNITE-3196 - ready for review

Ok, thanks for explanations. What about this task? 2017-02-07 13:57 GMT+03:00 Igor Sapego : > But that's Ok. Since we use int8_t for bytes in C++ as well I guess > your -0x80 may have more sense than 0x80. > > Best Regards, > Igor > > On Tue, Feb 7, 2017 at 1:54 PM, Igor

Re: Rethink native SQL API in Apache Ignite 2.0

+1 SqlFieldsQuery API is quite a convoluted way to do DML. 2.0 release should certainly address this. On Tue, Feb 7, 2017 at 2:34 PM, Vladimir Ozerov wrote: > Igniters, > > Our SQL engine becomes more and more sophisticated. Initially we had only > SELECTs, now we have

Rethink native SQL API in Apache Ignite 2.0

Igniters, Our SQL engine becomes more and more sophisticated. Initially we had only SELECTs, now we have DML, in AI 2.x we will have DDL. This is very cool, but it seems that we completely forgot about extending our native SQL API (IgniteCache.query, SqlQuery, SqlFieldsQuery) in response to

[jira] [Created] (IGNITE-4663) BinaryUtils.doReadObjectArray can not read array with platform-only element type

Pavel Tupitsyn created IGNITE-4663: -- Summary: BinaryUtils.doReadObjectArray can not read array with platform-only element type Key: IGNITE-4663 URL: https://issues.apache.org/jira/browse/IGNITE-4663

Re: IGNITE-3196 - ready for review

But that's Ok. Since we use int8_t for bytes in C++ as well I guess your -0x80 may have more sense than 0x80. Best Regards, Igor On Tue, Feb 7, 2017 at 1:54 PM, Igor Sapego wrote: > I was just curious. > > In C++ both constants 0x80 and -0x80 are of type 'int' and have

Re: IGNITE-3196 - ready for review

I was just curious. In C++ both constants 0x80 and -0x80 are of type 'int' and have the same lower byte, so they give the same result. Though first number is actually 0x0080 when the second one is 0xFF80. So it's just made a minus sign look a little redundant and pointless to me in C++

[jira] [Created] (IGNITE-4662) Server stores cache data on-heap if client has near cache

Semen Boikov created IGNITE-4662: Summary: Server stores cache data on-heap if client has near cache Key: IGNITE-4662 URL: https://issues.apache.org/jira/browse/IGNITE-4662 Project: Ignite

[jira] [Created] (IGNITE-4661) Optimizations: optimize PagesList.removeDataPage

Semen Boikov created IGNITE-4661: Summary: Optimizations: optimize PagesList.removeDataPage Key: IGNITE-4661 URL: https://issues.apache.org/jira/browse/IGNITE-4661 Project: Ignite Issue

[jira] [Created] (IGNITE-4660) Add DML capabilities to legacy JDBC driver

Alexander Paschenko created IGNITE-4660: --- Summary: Add DML capabilities to legacy JDBC driver Key: IGNITE-4660 URL: https://issues.apache.org/jira/browse/IGNITE-4660 Project: Ignite