Add new event in putblic API

HI all, I think what we need add new event for handling unhandled exception. We have some exception which not handled, new event (UnhandledExceptionEvent) can help know if was unhandled exception. Let's discuss. More details about reason IGNITE-2079

Re: Ignite TeamCity URL

Hi Igor, ci.ignite.apache.org 3 нояб. 2016 г. 11:26 PM пользователь "Igor Rudyak" написал: > Hi guys, > > Just curious what's the new URL for Ignite TeamCity? > > Igor >

Re: Ignite TeamCity URL

Yes, from this page wiki <https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Home>. On Thu, Nov 3, 2016 at 11:59 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Is this URL documented on Wiki? > > On Thu, Nov 3, 2016 at 1:52 PM, Dmitriy Govorukhi

Re: CachePojoStore data loading with binary marshaller

. > > Makes sense? > > -Val > > On Tue, Apr 11, 2017 at 12:06 PM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi all, > > > > I found problem related to CacheJdbcPojoStore. If try to load data, with > > enabled binary

TeamCity agent suspended

Hi guys, I have concerns about TC status, i see that 3 agent has overtime 80 h and 14 h. Who can restart them?

Re: TeamCity agent suspended

ri, Apr 7, 2017 at 10:55 AM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi guys, > > > > I have concerns about TC status, i see that 3 agent has overtime 80 h and > > 14 h. Who can restart them? > > >

CachePojoStore data loading with binary marshaller

Hi all, I found problem related to CacheJdbcPojoStore. If try to load data, with enabled binary marshaller, error may occur. Problem in entryMappings (this map helps resolve stored type when data loading). If binary marshaller disable we just put entry with java type in this map, if enable we

Re: Stable binary key representation

Hi guys, i implemented proxy for IgniteCache in hibernate integration, this proxy transformate cacheKey to our key wrapper, leaves only required field. I think we can remove identity resolve, it should not broke integration with hibernate. Any objections? On Wed, Mar 29, 2017 at 11:07 PM,

Re: Control.sh script and cluster activation

Denis, 1. control.sh have help parameter. If you try enter ./control.sh --help, result is an example of how to use it, "Example: --host {ip} --port {port} --{activate/deactivate} or without command --host {ip} --port {port} then will print status" 2. Visorcmd will start daemon node and join in

Re: Control.sh script and cluster activation

er results in a long stack trace... > >instead, it should provide a standard error message, suggesting > possible > >reasons for it. > > > > 4. Whenever trying to connect to a cluster, the script should print out a > message "Connecting to ip-address:port

Re: Control.sh script and cluster activation

Valentin, We have jira issue for this IGNITE-5586 <https://issues.apache.org/jira/browse/IGNITE-5586> On Tue, Aug 15, 2017 at 10:56 AM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > > Denis, > > 1. control.sh have help parameter. If you try enter ./con

Re: daemon nodes

What kind of messages are you talking about? Please, provide example. On Wed, Jun 28, 2017 at 11:54 AM, Дмитрий Рябов <somefire...@gmail.com> wrote: > Some messages don't go through clients. May be some daemon realization will > need them? > > 2017-06-28 11:22 GMT+03:00

Re: daemon nodes

Yakov, I created jira issue IGNITE-5603 . Whoever has an objection related this task? On Wed, Jun 28, 2017 at 2:28 PM, Yakov Zhdanov wrote: > >For me, daemon server, very strange. > > Agree, daemons can always be a

Persistent Distributed Store Metrics

Folk, As you know, ignite 2.1 will contain new module (pds), it will be provide ability to store data on disk. Let's discuss what type of metrics we need for this? I think it must be metrics per memory policy, per cache, checkpoint, and global metrics which will be aggregate all metrics. I did

daemon nodes

Hi Igniters, Can somebody explain what does mean daemon node? I thought that exist only client and server node, but node may can be daemon (server daemon or client daemon). As is can see, command line visor join in topology as server daemon. Can this be an outdated functionality?

Re: daemon nodes

r nodes, but does > not need to participate in computation or data related functionality. > > D. > > On Tue, Jun 27, 2017 at 2:49 AM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > >> Hi Igniters, >> >> Can somebody explain what does mean d

Re: method arguments code style

uidelines, however, I think we should > allow > > > the old style when the method signature (without throws clause) fits > the > > > line. > > > > > > Thoughts? > > > > > > 2018-05-03 12:09 GMT+03:00 Dmitry Pavlov <dpavlov@gmai

Re: async operation is not fair async

And as a next step I would think on > >> adopting async cache and SQL APIs. > >> > >> Vladimir. > >> > >> [1] > >> http://www.oracle.com/technetwork/database/ > application-development/jdbc/ > >> con1491-3961036.pdf > >> [2] http

Re: async operation is not fair async

the operation chain > inside a transaction. I see absolutely no point in maintaining this chain > outside of transactions. > > --AG > > 2018-05-14 16:01 GMT+03:00 Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> > : > > > Andrey, > > > >

Re: async operation is not fair async

roblem - deadlocks. We need to inform user > that this mode should be used with great care. > > On Fri, May 11, 2018 at 5:21 PM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Hi Igniters, > > > > I have a question. Why our async operation

Re: async operation is not fair async

olicy and so on. > > Best Regards, > Ivan Rakov > > > On 11.05.2018 18:18, Dmitriy Govorukhin wrote: > >> Vladimir, >> >> Should we create the new cache adapter or rework GridCacheAdapter? >> >> On Fri, May 11, 2018 at 5:52 PM, Vladimir Ozerov

Re: Disable WAL for several cache groups within one exchange

Ivan, Agree, if we have the batch method for cache create, we should have the ability to enable/disable WAL in the batch too. On Fri, May 11, 2018 at 5:17 PM, Ivan Rakov wrote: > Igniters, > > API method for disabling WAL in IgniteCluster accepts only one cache name. >

async operation is not fair async

Hi Igniters, I have a question. Why our async operation in not really async? GridCacheAdapter.syncOp has awaitLastFut(); this call wait last async operation completed. This means all async operation in one thread will be executed one by one but not in parallel. Async operation is not async.

Re: async operation is not fair async

Dmitriy S, If it will be in the internal package, and only for internal usage, are you agree with changes? пт, 11 мая 2018 г., 21:12 Dmitriy Setrakyan <dsetrak...@apache.org>: > On Fri, May 11, 2018 at 6:49 PM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrot

Re: async operation is not fair async

Dmitriy S, It is not broke existing code, because for use this ability you must use decorator "withFairSycn()". What about the argument of Vladimir? On Fri, May 11, 2018 at 8:41 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > On Fri, May 11, 2018 at 6:38 PM,

Re: async operation is not fair async

an Rakov > > > On 11.05.2018 18:30, Dmitriy Govorukhin wrote: > >> Ivan, >> >> My suggestion "withFairAsync()". What do you think? >> >> On Fri, May 11, 2018 at 6:23 PM, Ivan Rakov <ivan.glu...@gmail.com> >> wrote: >> >> I

Re: async operation is not fair async

Dmitriy S, Why method named as "async" but does not work as async? This is misleading. getAllAsync() is a special case. Not always you can use getAllAsync() instead of multiple getAsync(). In this topic, I wanna discuss problem not only for the GET operation but also all async operation behavior

Re: method arguments code style

looks very bad. My proposal was to allow two styles - first when all > arguments are on the same line splitted by 120 char limit, second when all > every arguments is on a separate line. > Mixed style should be disallowed. > > On Mon, May 7, 2018 at 12:35 AM, Dmitriy Govorukhin < &

Re: supporting different configuration format json,yaml...

configuration > > > > > > > > > > > >> and Spring approach in general. > > > > > > > > > > > >> > > > > > > > > > > > >> What will change is a XML formatting is goi

Re: Avoid JIRA comments deletion

+1 Dmitriy, I do not see any reason for deletion comments. Maybe only edit operation must be allowed. On Wed, May 16, 2018 at 12:32 PM, Igor Sapego wrote: > I totally agree. There is no sense in most cases in deletion > of commentaries. > > There is even less sense, when

Re: supporting different configuration format json,yaml...

n via XML Schema. We can surely hack this > around > > (I > > > bet there are existing libraries for configuring Spring with JSON), > but I > > > don't think that anyone suffered from inability to statically configure > > > Ignite with json/yaml. > > > >

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Dmitriy, Looks good for me please merge. On Tue, May 15, 2018 at 11:20 AM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Dmitriy, > > Ok, I will do it soon. > > On Mon, May 14, 2018 at 8:41 PM, Dmitry Pavlov <dpavlov@gmail.com> > wrote: >

Re: work with files and directories

d other components using > files. > > ср, 16 мая 2018 г. в 11:27, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com > >: > > > Andrey, > > > > My point is, it will be very cool if there is some component who will > know > > about persistence

work with files and directories

Hi Ignite, Do we have a general approach to work with a file and directories? I see many duplication logic for write through .tmp file. For example, GridCacheDatabaseSharedManager.writeCheckpointEntry(); GridCacheDatabaseSharedManage.nodeStart();

Re: async operation is not fair async

Alexey, Any updates? On Mon, May 14, 2018 at 6:19 PM, Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Alexey, > > Could you please add more description information for this task? [1] > Perhaps, base steps for implementation. > > [1] https://issues.apache.org

Re: work with files and directories

> > https://sonarcloud.io/component_measures?id=org. > > apache.ignite%3Aapache-ignite=duplicated_blocks& > > selected=org.apache.ignite%3Aignite-core%3Asrc%2Fmain% > > 2Fjava%2Forg%2Fapache%2Fignite%2Finternal%2Fprocessors%2Fcache% > > 2Fpersistence%2Fwal%2FFsyncModeFileW

Re: async operation is not fair async

(or whether we should delay this change to 3.0 at all). > > 2018-05-15 22:13 GMT+03:00 Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> > : > > > Alexey, > > > > Any updates? > > > > On Mon, May 14, 2018 at 6:19 PM, Dmitriy Govorukhin < > >

IGNITE-8583 - review needed

Igniters, I fixed DataStorageMetricsMXBean.getOffHeapSize, please review my changes. https://issues.apache.org/jira/browse/IGNITE-8583

Re: Baseline topology documentation clarified: usage scenarios and definition

+1 for a webinar, I would like to see it. On Wed, May 23, 2018 at 5:34 PM, Dmitry Pavlov wrote: > Hi Ivan, > > Would you like to run presentation based on this slides for Igniters? > > We can set up webinar using gotomeeting if you like this idea. > > Sincerely, > Dmitriy

Re: IGNITE-6430 (Done) CacheGroupsMetricsRebalanceTest.testRebalanceEstimateFinishTime test fails periodically

Dmitriy, Ok, I will do it soon. On Mon, May 14, 2018 at 8:41 PM, Dmitry Pavlov wrote: > Hi Dmitriy G, > > could you please pick up this review? > > Sincerely, > Dmitriy Pavlov > > чт, 10 мая 2018 г. в 15:50, Александр Меньшиков : > >> Hi, >> >> I

Re: Need review IGNITE-8661

! Very important fix to a very bad problem in the > product > > that could cause data consistency issue. > > > > Will it be included into 2.6, or will we have to wait for 2.7? > > > > D. > > > > On Thu, Jun 14, 2018 at 6:53 AM, Dmitriy Govorukhin &

unused or only used in tests methonds

Igniters, I found 2 methods, 1. PageStore.pageOffset(long pageId) - it unused, seem that old artifact. 2. IgnitePageStoreManager.pagesAllocated(int grpId) - used only in test, seem that same problem can be solved with IgnitePageStoreManager.pages(grpId, partId). I suggest, remove these methods

Re: WAL iterator unexpected behavior

t; different. I do not think it is OK to skip records during normal operation. > In my view, we should report an error and stop. However, when offline, it > is OK to report an error and continue in my view. > > D. > > On Wed, May 30, 2018 at 5:39 AM, Dmitriy Govorukhin < >

Re: WAL iterator unexpected behavior

Yakov, This problem is not for offline only, it applicable for all types of the iterators. In general, iterator does not know which class will be needed for deserialization. I guess we can expand WAL Iterator factory and provide a method for creating the iterator with some filter, which will

Re: WAL iterator unexpected behavior

. > > On Sun, Jun 3, 2018, 12:11 Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> > wrote: > > > Dmitriy, > > > > The iterator will be stopped. and method "it.next()" will throw the > > exception. > > > > On Sat, Jun 2, 2018 at 4

Re: WAL iterator unexpected behavior

Dmitriy, The iterator will be stopped. and method "it.next()" will throw the exception. On Sat, Jun 2, 2018 at 4:27 PM, Dmitriy Setrakyan wrote: > Dmitriy, what happens in case of unknown exceptions? > > > On Thu, May 31, 2018 at 6:35 AM, Dmitriy Govorukhin < >

IGNITE-8685 review request

Igniters, I prepared a rather important patch [1] related to WAL. In the current implementation, we calculation incorrect size for SEGMENT_SWITCH record, it leads to stopping the iteration at the end of a segment and iterator do not advance to the next segment. [1]

Re: Atomic cache inconsistent state

Denis, Seem that you right, it is a problem. I guess in this case primary node should send CachePartialUpdateException to near node. On Tue, Jun 5, 2018 at 6:13 PM, Denis Garus wrote: > Fix formatting > > Hello Igniters! > > I have found some confusing behavior of atomic partitioned cache with

Re: WAL iterator unexpected behavior

bility skip records by type or some pointer for the StandaloneWalRecordsIterator Comments are welcome. On Thu, May 31, 2018 at 12:53 AM, Dmitriy Setrakyan wrote: > On Wed, May 30, 2018 at 8:04 AM, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com> wrote: > > > Dmitriy, >

Re: Issues with forceServerMode on clients and unclear contract of isClient/isClientMode methods

Eduard, Sounds reasonable, agree with you. On Thu, May 31, 2018 at 5:10 PM, Eduard Shangareev < eduard.shangar...@gmail.com> wrote: > Hi, guys! > > I just have found that we widely > misuse org.apache.ignite.cluster.ClusterNode#isClient method. > > Now it returns how a node is connected to

Re: data extractor

ake a look. > > ticket - https://issues.apache.org/jira/browse/IGNITE-8485 > prototype - https://github.com/apache/ignite/pull/4167 > spi - > https://github.com/apache/ignite/pull/4167/files#diff-9a792ab0e6971f202d22d530af0ac933 > > В Сб, 30/06/2018 в 22:37 +0300, Dmitriy Govorukhin пишет: > &

Re: unused or only used in tests methonds

Igniters, If no one objects, then I delete these methods in next refactoring task. On Fri, Jun 15, 2018 at 6:38 PM Alexey Goncharuk wrote: > I have no objections to remove these methods. > > --AG > > чт, 14 июн. 2018 г. в 17:39, Dmitriy Govorukhin < > dmitriy

Re: Review request for IGNITE-8740: Support reuse of already initialized Ignite in IgniteSpringBean

Valentin, Seems that these changes have classes without license head. TC link

Re: Introduce a sample of activation policy when cluster is activated first time

Vladimir, Auto-activation on the first start? Please, shared an issue link if you have. On Tue, Jun 26, 2018 at 11:29 AM Vladimir Ozerov wrote: > Pavel, > > As far as I know we agreed to implement auto activation in one of the > nearest releases. Am I missing something? > > вт, 26 июня 2018 г.

data extractor

Igniters, I am working on IGNITE-7644 (export all key-value data from a persisted partition), it will be command line tool for extracting data from Ignite partition file without the need to start node. The main motivation is to have a lifebuoy

method arguments code style

Hi folks, I read https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines, but did not find anything about code style for method arguments. In many places in the code, I see different code style, this creates difficulties for reading. It seems to me an example below is rather

Re: Orphaned, duplicate, and main-class tests!

Ilya, I guess we can remove all these suites GridActivationAtomicCacheSuit GridActivationCacheAbstractTestSuit GridActivationLocalAndNearCacheSuit GridActivationPartitionedCacheSuit GridActivationReplicatedCacheSuit They became not relevant after standby mode became part of the basic

Re: Plugins in tests

Yakov, Agree, I created the issue for this. I will try to do it in the near future. IGNITE-7679 On Tue, Jan 30, 2018 at 8:40 AM, Yakov Zhdanov wrote: > Guys, > > When running tests from core module I see that Ignite

Re: async operation is not fair async

Folks, Any comments? I will start to implement withFairAsync(); decorator soon. On Wed, Aug 1, 2018 at 12:22 PM Dmitriy Pavlov wrote: > Igniters, > > I've re-read this thread in brief. As far as I know this change is not > coming from some company, so this change will be at least good for

Re: Quick questions on B+ Trees and Partitions

Hi John, 1. B + tree in a partition is a primary key index, this means that we use a B+ tree index for searching data in the partition. 2. Not fully understood a question, please explain more details. 3. It depends how many partitions do you have for these caches, by default it 1024 per cache, in

Re: StandaloneWalRecordsIterator: support iteration from custom pointer

Ivan, I implemented this issue, please review my changes. https://reviews.ignite.apache.org/ignite/review/IGNT-CR-729 On Thu, Aug 16, 2018 at 3:09 PM Ivan Rakov wrote: > Thanks for your comments! > I've created a ticket: https://issues.apache.org/jira/browse/IGNITE-9294 > > Best Regards, >

Re: data extractor

hes to upload to, etc. > > сб, 30 июн. 2018 г. в 22:38, Dmitriy Govorukhin < > dmitriy.govoruk...@gmail.com>: > > > Igniters, > > > > I am working on IGNITE-7644 > > <https://issues.apache.org/jira/browse/IGNITE-7644> (export all > key-value >

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

Re: New PMC member: Dmitriy Pavlov

Dmitriy, My congratulations! Thank you for your work! On Thu, Aug 30, 2018 at 1:58 PM Maxim Muzafarov wrote: > Dmitry, > > My congratulations! > Thank you for guiding and helping the community members and me, in > particular, > to follow the Apache Way principles and also for your

Thin client: transactions support

Hi, Igniters. I've seen a lot of discussions about thin client and binary protocol, but I did not hear anything about transactions support. Do we have some draft for this purpose? As I understand we have several problems: - thread and transaction have hard related (we use thread-local

Re: Memory usage per cache

Folks, I created 2 Jira issue for new metrics. Also, I think they will be useful. Let's discuss in comments. - Add new metrics for data storage IGNITE-8078 - Implement new JMX metrics for transactions IGNITE-8077

Re: Stop nodes after test by default - IGNITE-6842

Looks good for me, please merge. 19 мар. 2018 г. 3:22 ПП пользователь "Dmitry Pavlov" написал: > I agree it is important, I'm going to do a review, but do not have time > slot to do. > > Who could pick up this review? > > Dmitriy G., could I ask you? > > пн, 19 мар. 2018

Code inspection

Hi folks, Do we have 'inspection' [1] scheme for ignite? I see a lot of warnings in my code, and I guess it is because everyone uses different schemes. Let's start the discussion. [1] IDEA inspection

Re: Code inspection

8:15 +, Dmitry Pavlov пишет: > > Hi Dmitriy, > > > > I think we should resurrect thread about addition of code inspections, > and > > later we can enable automatic control step to TeamCity. > > > > Could you help me to find it? > > > > вт, 6 мар. 2

Re: jira issue filling rules

Vyacheslav, Thanks for links, I just wanted to remind these rules for all. Not all Igniters use these rules in work. On Mon, Oct 8, 2018 at 12:17 PM Vyacheslav Daradur wrote: > Hi Igniters, > > Dmitriy Govorukhin, the naming of GitHub PR [1] and Upsource review > [2] alrea

Re: Apache Ignite 2.7. Last Mile

gt; > > > > > > > > > > Nikolay, > > > > > > > > > > > > > > > > > > > > > > > > > > It completely breaks a major feature under certain > > > > > > > > > > conditions. >

jira issue filling rules

Hi folks, Recently time ago, I noticed that many Jira issues created and filled in different ways, so someone does not fill issue description, someone does not attach links in the links section instead, add links to comments and etc. I want to star discussion regards to Jira issue filling rules.

Re: [VOTE] Creation dedicated list for github notifiacations

+1 вт, 27 нояб. 2018 г., 19:41 Denis Mekhanikov dmekhani...@gmail.com: > +1 > I'm for making the dev list readable without filters of any kind. > > On Tue, Nov 27, 2018, 15:14 Maxim Muzafarov > > +1 > > > > Let's have a look at how it will be. > > > > On Tue, 27 Nov 2018 at 14:48 Seliverstov

Re: [DISCUSSION] Usage of system properties in tests

++1 from my side. I guess it will be a more reliable way for works with properties in the tests. From time to time somebody forgot clear property after test and next tests may be failed or flaky failed completion. On Thu, Feb 14, 2019 at 6:56 PM Dmitriy Pavlov wrote: > I find it absolutely

Re: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Hi all, Can we include https://issues.apache.org/jira/browse/IGNITE-12060? This is a https://issues.apache.org/jira/browse/IGNITE-11953 On Fri, Aug 9, 2019 at 10:04 AM Nikolay Izhikov wrote: > Hello, Deni. > > > Nickolay, could you check if that's a quick upgrade? > > Yes, I will take a look. >

Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Hi Alexey, I think that I will finish work on the fix tomorrow. Fix already completed but I need to get VISA from TC bot. On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk wrote: > Folks, it looks like I was overly optimistic with the estimates for the > mentioned two tickets. > > Dmitriy,

Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Hi Igniters, I finished work on https://issues.apache.org/jira/browse/IGNITE-12127, fix already in master and ignite-2.7.6 On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin < dmitriy.govoruk...@gmail.com> wrote: > Hi Alexey, > > I think that I will finish work on the fix tomorr

Re: Link to Grid Gain internal ticket in Ignite

Nikolay, my fault, already fixed. https://issues.apache.org/jira/browse/IGNITE-11998 On Thu, Jul 18, 2019 at 4:06 PM Nikolay Izhikov wrote: > Hello, Igniters. > > Dmitriy, can you, please, create an Ignite Jira ticket from your internal? > [1] > Or change link to existing Ignite ticket. > >

Re: [VOTE] Apache Ignite PMC Chair

+1 for Dmitry Pavlov сб, 2 нояб. 2019 г., 0:26 Alexey Goncharuk : > +1 for Alexey Goncharuk (binding) > > пн, 28 окт. 2019 г. в 21:06, Denis Magda : > > > Ignite community, > > > > Please cast a vote for one of the following candidates: > > > >- Alexey Goncharuk > >- Dmitry Pavlov > >

Re: [ANNOUNCE] New committer: Vyacheslav Koptilin

My congratulations, Slava! On Tue, Feb 18, 2020 at 11:33 PM Andrey Kuznetsov wrote: > Congratulations, Slava! > > вт, 18 февр. 2020 г. в 22:20, Dmitriy Pavlov : > > > Hello Ignite Community, > > > > The Project Management Committee (PMC) for Apache Ignite has invited > > Vyacheslav Koptilin to

Re: [VOTE] Allow or prohibit a joint use of @deprecated and @IgniteExperimental

-1 Prohibit On Mon, Feb 10, 2020 at 12:58 PM Pavel Tupitsyn wrote: > -1 Prohibit > > On Mon, Feb 10, 2020 at 12:41 PM Zhenya Stanilovsky > wrote: > > > > > -1, sounds confusing, i wan`t use deprecated API > > and @IgniteExperimental it`s something unknown with undefined «time for > > support».

[jira] [Created] (IGNITE-4044) Add an option to always authenticate local node

Dmitriy Govorukhin created IGNITE-4044: -- Summary: Add an option to always authenticate local node Key: IGNITE-4044 URL: https://issues.apache.org/jira/browse/IGNITE-4044 Project: Ignite

[jira] [Created] (IGNITE-4178) Support permission builder

Dmitriy Govorukhin created IGNITE-4178: -- Summary: Support permission builder Key: IGNITE-4178 URL: https://issues.apache.org/jira/browse/IGNITE-4178 Project: Ignite Issue Type

[jira] [Created] (IGNITE-4235) Can't get user exception if was on remote service

Dmitriy Govorukhin created IGNITE-4235: -- Summary: Can't get user exception if was on remote service Key: IGNITE-4235 URL: https://issues.apache.org/jira/browse/IGNITE-4235 Project: Ignite

[jira] [Created] (IGNITE-4931) Safe way for deactivate cluster.

Dmitriy Govorukhin created IGNITE-4931: -- Summary: Safe way for deactivate cluster. Key: IGNITE-4931 URL: https://issues.apache.org/jira/browse/IGNITE-4931 Project: Ignite Issue Type

[jira] [Created] (IGNITE-4919) Remove support BinaryIdentityResolver

Dmitriy Govorukhin created IGNITE-4919: -- Summary: Remove support BinaryIdentityResolver Key: IGNITE-4919 URL: https://issues.apache.org/jira/browse/IGNITE-4919 Project: Ignite Issue

[jira] [Created] (IGNITE-5019) Deadlock in GridCacheVariableTopologySelfTest.testNodeStop

Dmitriy Govorukhin created IGNITE-5019: -- Summary: Deadlock in GridCacheVariableTopologySelfTest.testNodeStop Key: IGNITE-5019 URL: https://issues.apache.org/jira/browse/IGNITE-5019 Project

[jira] [Created] (IGNITE-6074) Test fail IgniteWalRecoveryTest#testWalBigObjectNodeCancel

Dmitriy Govorukhin created IGNITE-6074: -- Summary: Test fail IgniteWalRecoveryTest#testWalBigObjectNodeCancel Key: IGNITE-6074 URL: https://issues.apache.org/jira/browse/IGNITE-6074 Project

[jira] [Created] (IGNITE-6082) Test fail DynamicIndexPartitionedTransactionalConcurrentSelfTest.testConcurrentPutRemove

Dmitriy Govorukhin created IGNITE-6082: -- Summary: Test fail DynamicIndexPartitionedTransactionalConcurrentSelfTest.testConcurrentPutRemove Key: IGNITE-6082 URL: https://issues.apache.org/jira/browse/IGNITE

[jira] [Created] (IGNITE-6064) Rework control.sh script.

Dmitriy Govorukhin created IGNITE-6064: -- Summary: Rework control.sh script. Key: IGNITE-6064 URL: https://issues.apache.org/jira/browse/IGNITE-6064 Project: Ignite Issue Type

[jira] [Created] (IGNITE-6052) Check cluster state from daemon node return incorrect cluster state

Dmitriy Govorukhin created IGNITE-6052: -- Summary: Check cluster state from daemon node return incorrect cluster state Key: IGNITE-6052 URL: https://issues.apache.org/jira/browse/IGNITE-6052

[jira] [Created] (IGNITE-6058) Test fail testTransformResourceInjection broken

Dmitriy Govorukhin created IGNITE-6058: -- Summary: Test fail testTransformResourceInjection broken Key: IGNITE-6058 URL: https://issues.apache.org/jira/browse/IGNITE-6058 Project: Ignite

[jira] [Created] (IGNITE-6098) Test fail IgniteDataIntegrityTests.testExpandBuffer

Dmitriy Govorukhin created IGNITE-6098: -- Summary: Test fail IgniteDataIntegrityTests.testExpandBuffer Key: IGNITE-6098 URL: https://issues.apache.org/jira/browse/IGNITE-6098 Project: Ignite

[jira] [Created] (IGNITE-5741) Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator

Dmitriy Govorukhin created IGNITE-5741: -- Summary: Replace HeapByteBuffer to DirectByteBuffer in WAL RecordsIterator Key: IGNITE-5741 URL: https://issues.apache.org/jira/browse/IGNITE-5741

[jira] [Created] (IGNITE-5603) All daemon node, can be only client daemon, server daemon is not allow.

Dmitriy Govorukhin created IGNITE-5603: -- Summary: All daemon node, can be only client daemon, server daemon is not allow. Key: IGNITE-5603 URL: https://issues.apache.org/jira/browse/IGNITE-5603

[jira] [Created] (IGNITE-5704) Do not allow cluster to be deactivated if the joining node does not complete start all components

Dmitriy Govorukhin created IGNITE-5704: -- Summary: Do not allow cluster to be deactivated if the joining node does not complete start all components Key: IGNITE-5704 URL: https://issues.apache.org/jira/browse

[jira] [Created] (IGNITE-5076) Optimization of multi-threaded start nodes in tests

Dmitriy Govorukhin created IGNITE-5076: -- Summary: Optimization of multi-threaded start nodes in tests Key: IGNITE-5076 URL: https://issues.apache.org/jira/browse/IGNITE-5076 Project: Ignite

[jira] [Created] (IGNITE-6015) Test fail in Ignite Cache 2: GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform

Dmitriy Govorukhin created IGNITE-6015: -- Summary: Test fail in Ignite Cache 2: GridCachePartitionedGetAndTransformStoreSelfTest.testGetAndTransform Key: IGNITE-6015 URL: https://issues.apache.org/jira

[jira] [Created] (IGNITE-5967) Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet

Dmitriy Govorukhin created IGNITE-5967: -- Summary: Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet Key: IGNITE-5967 URL: https://issues.apache.org/jira/browse/IGNITE-5967

[jira] [Created] (IGNITE-5968) Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead

Dmitriy Govorukhin created IGNITE-5968: -- Summary: Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead Key: IGNITE-5968 URL: https://issues.apache.org/jira/browse

  1   2   >