[jira] [Created] (IGNITE-10703) Queue drainTo should be batched operation

Dmitry Kiriy created IGNITE-10703: - Summary: Queue drainTo should be batched operation Key: IGNITE-10703 URL: https://issues.apache.org/jira/browse/IGNITE-10703 Project: Ignite Issue Type: Im

[jira] [Created] (IGNITE-10702) .NET: Ignite as Dotnet Core Global Tool

Pavel Tupitsyn created IGNITE-10702: --- Summary: .NET: Ignite as Dotnet Core Global Tool Key: IGNITE-10702 URL: https://issues.apache.org/jira/browse/IGNITE-10702 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-10701) add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest

Oleg Ignatenko created IGNITE-10701: --- Summary: add missing import to CacheQueryEntityWithJsr310Java8DateTimeApiFieldsTest Key: IGNITE-10701 URL: https://issues.apache.org/jira/browse/IGNITE-10701 Pr

[MTCGA]: new failures in builds [2550471, 2550461] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

Re: CONTRIBUTING.md first version

Sure, I will do пт, 14 дек. 2018 г., 20:37 Denis Magda : > > > > `Contributing.md` is more not about how to contribute in day by day > basis, > > but a short step-by-step guide on how to join and start contributing. > > > Could we rework and refine the wiki version in a similar way - most > impo

Re: REST GridCacheCommandHandler writes ERROR in log in case of bad user input

Hello! Thank you for the opinion! The following messages (Exception and its message) are fairly descriptive. Regards, -- Ilya Kasnacheev пт, 14 дек. 2018 г. в 21:35, Denis Magda : > Hello Ilya, > > It's fine to use ERROR level if an operation can't be completed due to > missing parameters. T

Re: REST GridCacheCommandHandler writes ERROR in log in case of bad user input

Hello Ilya, It's fine to use ERROR level if an operation can't be completed due to missing parameters. That's, in fact, an exception/error. What needs to be changed is texts of messages so that everyone understands what exactly happened and how to address a failure. -- Denis On Fri, Dec 14, 201

Re: Continuous queries and duplicates

Vladimir, Thanks for referring to the MVCC and Continuous Queries discussion, I knew that saw us discussing a solution of the duplication problem. Let me copy and paste it in here for others: 2) *Initial query*. We implemented it so that user can get some initial > data snapshot and then start re

[jira] [Created] (IGNITE-10700) [ML] Working with Binary Objects

Yury Babak created IGNITE-10700: --- Summary: [ML] Working with Binary Objects Key: IGNITE-10700 URL: https://issues.apache.org/jira/browse/IGNITE-10700 Project: Ignite Issue Type: Improvement

Re: CONTRIBUTING.md first version

> > `Contributing.md` is more not about how to contribute in day by day basis, > but a short step-by-step guide on how to join and start contributing. Could we rework and refine the wiki version in a similar way - most important stuff first, old is either removed and reworked. -- Denis On Fri,

[jira] [Created] (IGNITE-10699) Update documentation for control.sh

Sergey Antonov created IGNITE-10699: --- Summary: Update documentation for control.sh Key: IGNITE-10699 URL: https://issues.apache.org/jira/browse/IGNITE-10699 Project: Ignite Issue Type: Task

Re: Async debugging in IDEA

Looks cool, I will try пт, 14 дек. 2018 г. в 16:46, Павлухин Иван : > Hi Igniters, > > I would like to share with you that now it is possible to use IDEA > async debugger for debugging Ignite futures. And we should thank Ivan > Bessonov for that awesome contribution [1]. > > Most of your might be

Re: Apache Ignite TeamCity Bot - muted tests

We have IgniteIgnore, so we can use it. It seems behavior is the same. We need just to understand in which case we can get issue ID from TC REST (for the Bot). пт, 14 дек. 2018 г. в 17:51, Vyacheslav Daradur : > Dmitry Pavlov, > > As far as I know, we are able to use following construction to ign

Re: Page eviction for in-memory mode with enabled MVCC

Roman, I would prefer first option. The fact user uses MVCC says he needs some more strict guaranties which cannot meet in other modes. I would rollback both txs in case we cannot provide such guaranties. Regards, Igor пт, 14 дек. 2018 г. в 15:36, Roman Kondakov : > Vladimir, > > I was thinkin

[jira] [Created] (IGNITE-10698) Get rid of @MXBeanParametersNames and @MXBeanParametersDescriptions

Yakov Zhdanov created IGNITE-10698: -- Summary: Get rid of @MXBeanParametersNames and @MXBeanParametersDescriptions Key: IGNITE-10698 URL: https://issues.apache.org/jira/browse/IGNITE-10698 Project: Ig

[jira] [Created] (IGNITE-10697) [ML] Add Frequency Encoding

Aleksey Zinoviev created IGNITE-10697: - Summary: [ML] Add Frequency Encoding Key: IGNITE-10697 URL: https://issues.apache.org/jira/browse/IGNITE-10697 Project: Ignite Issue Type: New Feat

[jira] [Created] (IGNITE-10696) Java 9/10/11 Support [2.8]

Peter Ivanov created IGNITE-10696: - Summary: Java 9/10/11 Support [2.8] Key: IGNITE-10696 URL: https://issues.apache.org/jira/browse/IGNITE-10696 Project: Ignite Issue Type: Improvement

Re: Apache Ignite TeamCity Bot - muted tests

Dmitry Pavlov, As far as I know, we are able to use following construction to ignore test: Assume.assumeTrue("link-to-issue", false); On Fri, Dec 14, 2018 at 5:44 PM Dmitriy Pavlov wrote: > > Thank you, Dmitrii, > > I've started unmuting tests starting from yesterday. > > Now muted test count w

[jira] [Created] (IGNITE-10695) MVCC: Fix cache API conditional update operations.

Andrew Mashenkov created IGNITE-10695: - Summary: MVCC: Fix cache API conditional update operations. Key: IGNITE-10695 URL: https://issues.apache.org/jira/browse/IGNITE-10695 Project: Ignite

Re: Apache Ignite TeamCity Bot - muted tests

Thank you, Dmitrii, I've started unmuting tests starting from yesterday. Now muted test count was decreased from 3540 to 3408 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&tab=mutedProblems&branch_IgniteTests24Java8=%3Cdefault%3E Probably we could automate this activit

Re: Thin clients all in one

Hello again Starting to check compatibility between thin clients in java/c++ and py/php/nodejs and met some problems 1) Found that UUID mixed in a strange way if we taken it from Java/C++ to PY/PHP/JS client and backwards Have issue about it https://issues.apache.org/jira/browse/IGNITE-10691, ple

[jira] [Created] (IGNITE-10694) MVCC: Possible recycled pages leak.

Roman Kondakov created IGNITE-10694: --- Summary: MVCC: Possible recycled pages leak. Key: IGNITE-10694 URL: https://issues.apache.org/jira/browse/IGNITE-10694 Project: Ignite Issue Type: Bug

Apache Ignite TeamCity Bot - muted tests

Hello, Igniters! Our Bot got new functionality - it shows tests muted on TeamCity and their ticket status [1]. So, we can see forgotten mutes for resolved tickets now. Igniters with rights to unmute tests on TC - please, check this page periodically for forgotten mutes. [1] https://mtcga.gridga

[jira] [Created] (IGNITE-10693) MVCC TX: Random server restart tests became failed

Igor Seliverstov created IGNITE-10693: - Summary: MVCC TX: Random server restart tests became failed Key: IGNITE-10693 URL: https://issues.apache.org/jira/browse/IGNITE-10693 Project: Ignite

[jira] [Created] (IGNITE-10692) MVCC: Test GridCacheDhtPreloadDelayedSelfTest fails in mvcc mode.

Andrew Mashenkov created IGNITE-10692: - Summary: MVCC: Test GridCacheDhtPreloadDelayedSelfTest fails in mvcc mode. Key: IGNITE-10692 URL: https://issues.apache.org/jira/browse/IGNITE-10692 Project

Async debugging in IDEA

Hi Igniters, I would like to share with you that now it is possible to use IDEA async debugger for debugging Ignite futures. And we should thank Ivan Bessonov for that awesome contribution [1]. Most of your might be already familiar with async debugger in IDEA. For the rest I prepared two screens

REST GridCacheCommandHandler writes ERROR in log in case of bad user input

Hello! It seems that we have subj behavior since the earliest days if Apache Ignite. If you send a REST command with error in it (such as missing "keys" for getAll), you will get a nice [2018-10-30 22:22:14,021][ERROR][rest-#61061][GridCacheCommandHandler] Failed to execute cache command: GridRes

[jira] [Created] (IGNITE-10691) thin clients: PY, PHP and NodeJS clients different UUID format

Stepan Pilschikov created IGNITE-10691: -- Summary: thin clients: PY, PHP and NodeJS clients different UUID format Key: IGNITE-10691 URL: https://issues.apache.org/jira/browse/IGNITE-10691 Project

[jira] [Created] (IGNITE-10690) Ignite throws exception when storing an object with an Instant field

Benjamin Dunton created IGNITE-10690: Summary: Ignite throws exception when storing an object with an Instant field Key: IGNITE-10690 URL: https://issues.apache.org/jira/browse/IGNITE-10690 Projec

Re: Continuous queries and duplicates

Guys, FYI: Partition counters are already a part of the public API. The following method reveals this information: CacheQueryEntryEvent#getPartitionUpdateCounter()

Re: Code inspection

Maxim, PR is incomplete. Some plugins should be disabled with different id\name. Maven plugin shouldn't be disabled as Idea Inspector use it to use Ignite project pom file. Please, find details in ticket. On Fri, Dec 14, 2018 at 12:00 PM Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: >

Re: Is it time to move forward to JUnit4 (5)?

Hi Ivan, The issues you mentioned are real and these issues are expected to be addressed per IGNITE-10177. I am currently experimenting with various approaches to tackle that, will post here when "early preview implementation" is ready to let others take a look and test it. Until this is complet

Re: Page eviction for in-memory mode with enabled MVCC

Vladimir, I was thinking about your proposal to not evict locked and recent (the transaction that created the record is still active) entries from the cache. Let's imagine next situation: we have almost full memory and two transactions: 1. txA: "SELECT * FOR UPDATE" 2. txB: "INSERT ...many

Re: Page eviction for in-memory mode with enabled MVCC

Hi Ivan, of course, prohibiting eviction for MVCC caches is the simplest way. But if we can implement the same feature for MVCC cache, why shouldn't we do it? Users may want to use MVCC caches as in-memory caching layer in their applications. And if they want so, I do not see anything against

Re: Is it time to move forward to JUnit4 (5)?

Hi guys, I started writing a junit4 test for a feature I am currently working on. And immediately I faced a peculiarity with @Before test fixture. I automatically named a method "setUp" and realized that I override a method from a superclass. It can produce unwanted effects. First, it looks reason

[jira] [Created] (IGNITE-10689) Expose IO statistics for run query

Yury Gerzhedovich created IGNITE-10689: -- Summary: Expose IO statistics for run query Key: IGNITE-10689 URL: https://issues.apache.org/jira/browse/IGNITE-10689 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-10688) Expose SQL views for IO statistics

Yury Gerzhedovich created IGNITE-10688: -- Summary: Expose SQL views for IO statistics Key: IGNITE-10688 URL: https://issues.apache.org/jira/browse/IGNITE-10688 Project: Ignite Issue Type:

Re: Pre-touch for Ignite off-heap memory

Bump. Stanislav, Ivan, can you answer my questions? Let's discuss these improvements. ср, 12 дек. 2018 г. в 22:14, Павлухин Иван : > Hi Stan, > > As I participated in discussion in current thread I would like to > leave a comment. > > Your concerns looks clear for me and if you believe that pre-

[jira] [Created] (IGNITE-10687) Document new JMX bean wchih expose IO statistics.

Yury Gerzhedovich created IGNITE-10687: -- Summary: Document new JMX bean wchih expose IO statistics. Key: IGNITE-10687 URL: https://issues.apache.org/jira/browse/IGNITE-10687 Project: Ignite

[jira] [Created] (IGNITE-10686) NPE on query execution on node kill

Pavel Voronkin created IGNITE-10686: --- Summary: NPE on query execution on node kill Key: IGNITE-10686 URL: https://issues.apache.org/jira/browse/IGNITE-10686 Project: Ignite Issue Type: Bug

Re: CONTRIBUTING.md first version

Thank you for sharing your vision, I also agree to have short in GH and full in the wiki. Denis, I see a number of outdated info in How To Contribute, but most sections there are for a strong reason. A lot of cases covered, and a lot of cases could be covered in addition to existing. `Contributin

Re: Page eviction for in-memory mode with enabled MVCC

Hi folks, I did not quite get what user problem we are trying to solve so far. The simplest thing which comes to my mind is to prohibit MVCC caches creation in a data region with eviction configured. What am I missing? Why do we need this feature today? чт, 13 дек. 2018 г. в 22:33, Vladimir Ozero

[jira] [Created] (IGNITE-10685) Support JTA transactions for MVCC

Ivan Pavlukhin created IGNITE-10685: --- Summary: Support JTA transactions for MVCC Key: IGNITE-10685 URL: https://issues.apache.org/jira/browse/IGNITE-10685 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-10684) Memory leak in persistent IgniteSet

Alexey Belov created IGNITE-10684: - Summary: Memory leak in persistent IgniteSet Key: IGNITE-10684 URL: https://issues.apache.org/jira/browse/IGNITE-10684 Project: Ignite Issue Type: Bug

Re: Code inspection

Maxim, Thanks, I'll check PR and let you know about results. For now, Inspections task execution time looks much better (15-22 min), but fluctuation is still noticeable. On Fri, Dec 14, 2018 at 11:13 AM Maxim Muzafarov wrote: > Andrey, > > Thanks! I've consulted with the IntelliJ IDEA source c

[jira] [Created] (IGNITE-10683) Prepare process of packaging and delivering thin clients

Peter Ivanov created IGNITE-10683: - Summary: Prepare process of packaging and delivering thin clients Key: IGNITE-10683 URL: https://issues.apache.org/jira/browse/IGNITE-10683 Project: Ignite

Re: Service grid redesign

>*1. Testing of the cache-based implementation of the service grid.* > I think, we should make a test suite, that will test the old implementation > until we remove it from the project. Agree. This is exactly what should be done as the first step once phase 1 will be merged. I think all tests in t

Re: CONTRIBUTING.md first version

Agree. GitHub can have shorter quick notes with link to full documentation. > On 14 Dec 2018, at 08:05, Alexey Kuznetsov wrote: > > Hi, > > From my experience it is better when all needed stuff available on GitHub. > > It is very comfortable when thinks like, "read me", "change log", "how to

Re: Code inspection

Andrey, Thanks! I've consulted with the IntelliJ IDEA source code and found how this disabled plugins file should look like. I've created a new issue [1] and prepared PR [2] with the set of disabled plugins (maybe not complete set). I don't have access to change corresponding `~Excluded [Inspectio