Good news, Anton! Thanks for your work on PME feature!
> 19 дек. 2019 г., в 21:00, Anton Vinogradov <a...@apache.org> написал(а): > > Folks, > "2.8 + cherrypicked pme-free switch" vs "2.8" check finished, no blockers > found. > https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull%2F7165%2Fhead&action=Latest&baseBranchForTc=pull%2F7102%2Fhead > Any objections to merging? > > On Thu, Dec 19, 2019 at 4:20 PM Вячеслав Коптилин <slava.kopti...@gmail.com> > wrote: > >> Hello Pavel, >> >> Good to hear from you! >> >>> I guess we should have a system property to have ability to turn off PME >> free switch behavior if something goes wrong after release. >>> After feature battle testing we can remove it in the next release. >> Sounds good to me. >> >> Thanks, >> S. >> >> чт, 19 дек. 2019 г. в 15:59, Pavel Kovalenko <jokse...@gmail.com>: >> >>> Anton, Slava >>> >>> I guess we should have a system property to have ability to turn off PME >>> free switch behavior if something goes wrong after release. >>> After feature battle testing we can remove it in the next release. >>> >>> чт, 19 дек. 2019 г. в 15:26, Anton Vinogradov <a...@apache.org>: >>> >>>> Slava, >>>> >>>>>> It would be nice to cut off a new branch from the release and run >> all >>>> the >>>>>> tests with an integrated feature and after that, >>>>>> if you don’t see new failures and the release engineer agrees with >> the >>>>>> result, then and only then this feature can be merged into the >>> release. >>>> I fully agree and see no other way to perform this. >>>> PR already created and testing check scheduled. >>>> >>>> But, Maxim's proposal was to perform checks at the master branch >>>> >>>>>> 1. Merge the issue to the master branch. >>>>>> 2. Wait for two-three weeks of running tests. >>>>>> 3. Check that there are not flaky failures and fix them all >> otherwise. >>>>>> 4. Cherry-pick commit to the ignite-2.8 branch. >>>> >>>> and that's the point of discussion. >>>> >>>> On Thu, Dec 19, 2019 at 3:14 PM Вячеслав Коптилин < >>>> slava.kopti...@gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>>> We're releasing release branch, not master... why we're checking >> the >>>>> "wrong" branch? :) >>>>>> Performing the release verification we're checking not only how >>>> features >>>>> work, but also how they work together. >>>>> Yep, I agree that we should do verification for both branches of >> corse. >>>>> >>>>>> Finally, my concerns mostly related to integration checks and fail >>>>> hidings, not feature checks. >>>>>> That's why I propose to start integration checks asap. >>>>> IMHO, that is not the right way in order to handle such cases. >>>>> Cherry-picking new features into the release branch directly without >>> the >>>>> integration branch is not about STABILITY (this is normal and >>> acceptable >>>> to >>>>> cherry-pick obvious/trivial fixes into the release branch, though). >>>>> It would be nice to cut off a new branch from the release and run all >>> the >>>>> tests with an integrated feature and after that, >>>>> if you don’t see new failures and the release engineer agrees with >> the >>>>> result, then and only then this feature can be merged into the >> release. >>>>> >>>>> This is my own view of the matter, and I do not insist that you >> should >>>> act >>>>> in this way, but it seems to me that it would be safer and more >>> correct. >>>>> >>>>> Thanks, >>>>> S. >>>>> >>>>> чт, 19 дек. 2019 г. в 14:20, Anton Vinogradov <a...@apache.org>: >>>>> >>>>>> Feature already tested at the feature branch properly. >>>>>> Question is about master -> release merge. >>>>>> >>>>>> So: >>>>>> 1) Testing at master does not equal to testing at release. >>>>>> Code may fail in the master while it works at the release branch >> and >>>> vice >>>>>> versa. >>>>>> >>>>>> 2) Master is flakier that release branch, so we able to miss >> problem >>>>> hidden >>>>>> by other failures. >>>>>> >>>>>> Summarizing, >>>>>> We're releasing release branch, not master... why we're checking >> the >>>>>> "wrong" branch? :) >>>>>> Performing the release verification we're checking not only how >>>> features >>>>>> work, but also how they work together. >>>>>> We may have different race condition windows at different branched. >>>>>> The bug may never happen at master, but happen each 50th check at >>> 2.8, >>>>> and >>>>>> in case we'll delay feature merge and check 2.8 only 49 times >> (while >>> we >>>>>> have 150+ successful checks at master) we gain false-negative case >>> for >>>>> 2.8. >>>>>> >>>>>> Finally, my concerns mostly related to integration checks and fail >>>>> hidings, >>>>>> not feature checks. >>>>>> That's why I propose to start integration checks asap. >>>>>> >>>>>> On Thu, Dec 19, 2019 at 1:21 PM Вячеслав Коптилин < >>>>>> slava.kopti...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Hello Anton, >>>>>>> >>>>>>>> We always have to merge all release features asap to have as >> much >>>>> time >>>>>> as >>>>>>> possible to fix all bugs. >>>>>>> Could you please clarify this? What is the reason for that asap >>>>> merging, >>>>>>> especially the merging into the release branch? >>>>>>> Why the testing cannot be done on the feature branch? You always >>> have >>>>> an >>>>>>> ability to run RunAll/RunAllNightly builds on the feature branch >>> and >>>>> "fix >>>>>>> all bugs". >>>>>>> >>>>>>> Please don't get me wrong, I don't have objections/concerns >> related >>>> to >>>>>> the >>>>>>> 'pme-free-switch' feature itself. I do not quite understand the >>>>>> motivation >>>>>>> for that zerg rush. >>>>>>> >>>>>>> Thanks, >>>>>>> S. >>>>>>> >>>>>>> ср, 18 дек. 2019 г. в 23:23, Anton Vinogradov <a...@apache.org>: >>>>>>> >>>>>>>> Sure, >>>>>>>> You may count on my assistance in case of any problems. >>>>>>>> We're both in the same boat. >>>>>>>> >>>>>>>> But I see no reason to delay the "pme-free switch" merge to >> 2.8. >>>>>>>> We always have to merge all release features asap to have as >> much >>>>> time >>>>>> as >>>>>>>> possible to fix all bugs. >>>>>>>> >>>>>>>> I will replace the "feature activation version" with the >>>>> "IgniteFeature >>>>>>>> approach" according to your hint and merge it to master and 2.8 >>>>> shortly >>>>>>> in >>>>>>>> case of no objections here. >>>>>>>> >>>>>>>> On Wed, Dec 18, 2019 at 2:16 PM Maxim Muzafarov < >>> mmu...@apache.org >>>>> >>>>>>> wrote: >>>>>>>> >>>>>>>>> Folks, >>>>>>>>> >>>>>>>>> I have no objections. But I would like to count on your >> support >>>> in >>>>>>>>> cases of any release-blocking issues. Can I? >>>>>>>>> >>>>>>>>> >>>>>>>>> Anton, >>>>>>>>> >>>>>>>>> Let's do the following: >>>>>>>>> 1. Merge the issue to the master branch. >>>>>>>>> 2. Wait for two-three weeks of running tests. >>>>>>>>> 3. Check that there are not flaky failures and fix them all >>>>>> otherwise. >>>>>>>>> 4. Cherry-pick commit to the ignite-2.8 branch. >>>>>>>>> >>>>>>>>> WDYT? >>>>>>>>> >>>>>>>>> On Wed, 18 Dec 2019 at 09:26, Nikolay Izhikov < >>>> nizhi...@apache.org >>>>>> >>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> +1 to include PME free switch to 2.8 >>>>>>>>>> >>>>>>>>>> ср, 18 дек. 2019 г., 8:31 Anton Vinogradov <a...@apache.org >>> : >>>>>>>>>> >>>>>>>>>>> Maxim, >>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-9913 >>> (Pme-free >>>>>>> switch) >>>>>>>>> ready >>>>>>>>>>> to be merged to master. >>>>>>>>>>> How about to include it to the 2.8 too? >>>>>>>>>>> >>>>>>>>>>> On Tue, Dec 17, 2019 at 3:31 PM Ivan Pavlukhin < >>>>>>> vololo...@gmail.com> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Maxim, >>>>>>>>>>>> >>>>>>>>>>>> I cherry-picked >>>>>>> https://issues.apache.org/jira/browse/IGNITE-12424 >>>>>>>>> to >>>>>>>>>>>> 2.8 branch. >>>>>>>>>>>> >>>>>>>>>>>> вт, 17 дек. 2019 г. в 15:23, Ivan Pavlukhin < >>>>>> vololo...@gmail.com >>>>>>>> : >>>>>>>>>>>>> >>>>>>>>>>>>> Maxim, >>>>>>>>>>>>> >>>>>>>>>>>>> Regarding blocker tickets: >>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-2176 -- >>>> moved >>>>>> to >>>>>>>> next >>>>>>>>>>>> version >>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-8552 -- >>>> moved >>>>>> to >>>>>>>> next >>>>>>>>>>>> version >>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-9489 -- >>>> fixed >>>>>> in >>>>>>>>> scope of >>>>>>>>>>>>> another ticket >>>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-2176 -- >>>> Anton >>>>>> K. >>>>>>> is >>>>>>>>> going >>>>>>>>>>>>> to fix it in next few days >>>>>>>>>>>>> >>>>>>>>>>>>> вт, 17 дек. 2019 г. в 13:30, Maxim Muzafarov < >>>>>>> mmu...@apache.org >>>>>>>>> : >>>>>>>>>>>>>> >>>>>>>>>>>>>> Ivan, >>>>>>>>>>>>>> >>>>>>>>>>>>>> You should cherry-pick this commit to the >> ignite-2.8 >>>>> branch >>>>>>>> also. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Can you help with the release blocker issue >> mentioned >>>>>> above? >>>>>>> I >>>>>>>>> can >>>>>>>>>>> not >>>>>>>>>>>>>> found the people who are assigned those issues. We >>> need >>>>> to >>>>>>>>> clarify >>>>>>>>>>>>>> issues status and ask for help if necessary. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Tue, 17 Dec 2019 at 11:33, Ivan Pavlukhin < >>>>>>>>> vololo...@gmail.com> >>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Maxim, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> I merged a fix for thin JDBC default query >> timeout >>> to >>>>>>> master >>>>>>>>> under >>>>>>>>>>>>>>> [1]. What should be the next steps with regard to >>> 2.8 >>>>>>> release >>>>>>>>>>> branch? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> [1] >>>> https://issues.apache.org/jira/browse/IGNITE-12424 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> чт, 12 дек. 2019 г. в 13:08, Maxim Muzafarov < >>>>>>>>> mmu...@apache.org>: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Igniters, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Here are the 2.8 release BLOCKER issues with >>>> unknown >>>>>>> status >>>>>>>>> for >>>>>>>>>>> me. >>>>>>>>>>>>>>>> If anyone knows details can you share it? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> IGNITE-2176 [1] - Not valid exceptions in the >>> case >>>>> when >>>>>>>>> example >>>>>>>>>>>> can't >>>>>>>>>>>>>>>> works (Java 8) >>>>>>>>>>>>>>>> IGNITE-8552 [2] - Unable to use a date as >> primary >>>> key >>>>>>>>>>>>>>>> IGNITE-12227 [3] - Default auto-adjust baseline >>>>> enabled >>>>>>>> flag >>>>>>>>>>>>>>>> calculated incorrectly in some cases >>>>>>>>>>>>>>>> IGNITE-9489 [4] - CorruptedTreeException on >>> index >>>>>>> create. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [1] >>>>> https://issues.apache.org/jira/browse/IGNITE-2176 >>>>>>>>>>>>>>>> [2] >>>>> https://issues.apache.org/jira/browse/IGNITE-8552 >>>>>>>>>>>>>>>> [3] >>>>> https://issues.apache.org/jira/browse/IGNITE-12227 >>>>>>>>>>>>>>>> [4] >>>>> https://issues.apache.org/jira/browse/IGNITE-9489 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, 12 Dec 2019 at 07:05, Saikat Maitra < >>>>>>>>>>>> saikat.mai...@gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Hi Ivan, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thank you so much for your help, I really >>>>> appreciate >>>>>>> it. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I had a quick question and shared in the Jira >>>> issue >>>>>>>>>>>>>>>>> >>>> https://issues.apache.org/jira/browse/IGNITE-12424 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Please review and share your feedback. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>> Saikat >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Wed, Dec 11, 2019 at 3:45 AM Ivan >> Pavlukhin >>> < >>>>>>>>>>>> vololo...@gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Saikat, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Please see my comment in ticket [1]. Also >> you >>>> can >>>>>>> count >>>>>>>>> on my >>>>>>>>>>>>>>>>>> assistance for the subject. Currently I >> have >>>> time >>>>>> to >>>>>>>> help >>>>>>>>>>> with >>>>>>>>>>>> it. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> [1] >>>>>>> https://issues.apache.org/jira/browse/IGNITE-12424 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> вт, 10 дек. 2019 г. в 06:15, Saikat Maitra >> < >>>>>>>>>>>> saikat.mai...@gmail.com>: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Ilya, Ivan >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thank you for looping me in, I was >> looking >>>> into >>>>>>> this >>>>>>>>> issue >>>>>>>>>>>>>>>>>>> >>>>>> https://issues.apache.org/jira/browse/IGNITE-12424 >>>>>>>> and >>>>>>>>>>>> looked into >>>>>>>>>>>>>>>>>>> JdbcRequest and JdbcRequestHandler but I >> do >>>> not >>>>>> see >>>>>>>> the >>>>>>>>>>>> timeout field. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I was hoping the fix would be something >>>> similar >>>>>> to >>>>>>>>> adding >>>>>>>>>>>> these 2 lines >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/odbc/OdbcRequestHandler.java#L348-L349 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Can you please confirm if the Jdbc client >>>> side >>>>>>>> timeout >>>>>>>>> is >>>>>>>>>>>> even passed to >>>>>>>>>>>>>>>>>>> server? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I am fine to exclude >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-7285 >>>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>>>> make the release 2.8.0. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>>>> Saikat >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Mon, Dec 9, 2019 at 11:52 AM Вячеслав >>>>>> Коптилин < >>>>>>>>>>>>>>>>>> slava.kopti...@gmail.com> >>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Hello Ilya, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Looks like the same issue as >>>>>>>>>>>>>>>>>>>> >>>>>>> https://issues.apache.org/jira/browse/IGNITE-12419 >>>>>>>>>>>>>>>>>>>> This case should be covered by TCK >> tests. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>>>> S. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> пн, 9 дек. 2019 г. в 20:16, Ilya >>>> Kasnacheev < >>>>>>>>>>>> ilya.kasnach...@gmail.com >>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Hello! >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I have found a regression to 2.7 >> which >>>>>>>>> unfortunately >>>>>>>>>>> was >>>>>>>>>>>> not caught >>>>>>>>>>>>>>>>>> by >>>>>>>>>>>>>>>>>>>> our >>>>>>>>>>>>>>>>>>>>> tests: >>>>>>>>>>>>>>>>>>>>> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-12428 >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> It would be nice to fix it before >>>> releasing >>>>>>> 2.8. >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Regards, >>>>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>>>> Ilya Kasnacheev >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> пн, 9 дек. 2019 г. в 14:58, Ivan >>>> Pavlukhin >>>>> < >>>>>>>>>>>> vololo...@gmail.com>: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Maxim, >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I see the issue [1] is >> unassigned. >>> Do >>>>> we >>>>>>>> have a >>>>>>>>>>>> person who will >>>>>>>>>>>>>>>>>> fix >>>>>>>>>>>>>>>>>>>> it >>>>>>>>>>>>>>>>>>>>>>> bravely? :) >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Let's wait Saikat as an original >>> ticket >>>>>>>>> contributor. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> P.S. The issue [1] doesn't seem >> to >>>> be a >>>>>>> truly >>>>>>>>>>>> release `blocker`. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> For me it sounds not good to >>>>> intentionally >>>>>>>>> include >>>>>>>>>>>> such behavior >>>>>>>>>>>>>>>>>> into >>>>>>>>>>>>>>>>>>>>>> product release. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> пн, 9 дек. 2019 г. в 13:26, Maxim >>>>>> Muzafarov < >>>>>>>>>>>> mmu...@apache.org>: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Ivan, >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> I see the issue [1] is >> unassigned. >>> Do >>>>> we >>>>>>>> have a >>>>>>>>>>>> person who will >>>>>>>>>>>>>>>>>> fix >>>>>>>>>>>>>>>>>>>> it >>>>>>>>>>>>>>>>>>>>>>> bravely? :) >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> If not I think it's better to >>> revert >>>>> the >>>>>>>> issue >>>>>>>>> from >>>>>>>>>>>> the 2.8 >>>>>>>>>>>>>>>>>> release >>>>>>>>>>>>>>>>>>>>>>> branch and fix it in a calm >> manner >>> in >>>>> the >>>>>>>>> master >>>>>>>>>>>> branch. I >>>>>>>>>>>>>>>>>> suppose >>>>>>>>>>>>>>>>>>>>>>> there will be enough of such >>> changes >>>> to >>>>>>>>> perform a >>>>>>>>>>>> next minor >>>>>>>>>>>>>>>>>> release >>>>>>>>>>>>>>>>>>>>>>> (e.g. 2.8.1) with such fixes. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> P.S. The issue [1] doesn't seem >> to >>>> be a >>>>>>> truly >>>>>>>>>>>> release `blocker`. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-12424 >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On Mon, 9 Dec 2019 at 11:39, Ivan >>>>>>> Pavlukhin < >>>>>>>>>>>> vololo...@gmail.com >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Saikat, igniters >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> I raised a blocker [1] for 2.8 >>>>> related >>>>>> to >>>>>>>>>>> recently >>>>>>>>>>>> implemented >>>>>>>>>>>>>>>>>>>>> default >>>>>>>>>>>>>>>>>>>>>>>> query timeout [2]. Currently we >>>> have >>>>> a >>>>>>>> buggy >>>>>>>>>>>> behavior for thin >>>>>>>>>>>>>>>>>> JDBC >>>>>>>>>>>>>>>>>>>>>>>> driver when a default timeout >> is >>>>>>>> configured. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Actually I see 2 options to go: >>>>>>>>>>>>>>>>>>>>>>>> 1. Fix the issue with thin JDBC >>>> [1]. >>>>>>>>>>>>>>>>>>>>>>>> 2. Exclude a default query >>> timeout >>>>>>> support >>>>>>>>> [2] >>>>>>>>>>>> from 2.8. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Please share your thoughts! >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-12424 >>>>>>>>>>>>>>>>>>>>>>>> [2] >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-7285 >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> пт, 6 дек. 2019 г. в 19:55, >> Maxim >>>>>>>> Muzafarov < >>>>>>>>>>>> mmu...@apache.org >>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Slava, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Thanks for noticing. I think >> we >>>> can >>>>>>>> include >>>>>>>>>>> both >>>>>>>>>>>> of them. >>>>>>>>>>>>>>>>>>>>>>>>> Do you need any help from my >>>> side? >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> On Fri, 6 Dec 2019 at 14:02, >>>>> Вячеслав >>>>>>>>> Коптилин >>>>>>>>>>> < >>>>>>>>>>>>>>>>>>>>>> slava.kopti...@gmail.com> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Hello Maxim, >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> I found two issues that >>> should >>>> be >>>>>>>>> included in >>>>>>>>>>>> the upcoming >>>>>>>>>>>>>>>>>> AI >>>>>>>>>>>>>>>>>>>>> 2.8, >>>>>>>>>>>>>>>>>>>>>> I think. >>>>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-12409 - >>>>>>>>>>>>>>>>>>>>> Already >>>>>>>>>>>>>>>>>>>>>> done and >>>>>>>>>>>>>>>>>>>>>>>>>> can be cherry-picked into >> the >>>>>> release >>>>>>>>> branch. >>>>>>>>>>>>>>>>>>>>>>>>>> [2] >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-12419 - >>>>>>>>>>>>>>>>>> This >>>>>>>>>>>>>>>>>>>>>> one looks >>>>>>>>>>>>>>>>>>>>>>>>>> like a blocker for the >>> release. >>>>>>>>> Pull-request >>>>>>>>>>>> is available. >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>>>>>>>>>>>>> S. >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>> вт, 3 дек. 2019 г. в 15:30, >>>>> Alexei >>>>>>>>>>> Scherbakov < >>>>>>>>>>>>>>>>>>>>>> alexey.scherbak...@gmail.com >>>>>>>>>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> No objections. >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> вт, 3 дек. 2019 г. в >> 15:02, >>>>> Maxim >>>>>>>>>>> Muzafarov < >>>>>>>>>>>>>>>>>>>> mmu...@apache.org >>>>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Alexey, >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Yet another issue [1] >>> with >>>>>>>> corrupted >>>>>>>>>>>> B+Tree exception >>>>>>>>>>>>>>>>>> on >>>>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>>>>>> master >>>>>>>>>>>>>>>>>>>>>>>>>>> branch. >>>>>>>>>>>>>>>>>>>>>>>>>>>> My suggestion is to >>> revert >>>>> the >>>>>>>>>>>> IGNITE-11704 [3] issue >>>>>>>>>>>>>>>>>> from >>>>>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>>>>>> master >>>>>>>>>>>>>>>>>>>>>>>>>>>> branch and rework the >>>> patch. >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Any objections? >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Configuration: >>>>>>>>>>>>>>>>>>>>>>>>>>>> [1] persistence = false >>>>>>>>>>>>>>>>>>>>>>>>>>>> [2] persistence = true >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> class >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException: >>>>>>>>>>>>>>>>>>>>>>>>>>>> B+Tree is corrupted >>>>>>> [pages(groupId, >>>>>>>>>>>>>>>>>> pageId)=[IgniteBiTuple >>>>>>>>>>>>>>>>>>>>>>>>>>>> [val1=1544803905, >>>>>>>>> val2=844420635196573]], >>>>>>>>>>>> msg=Runtime >>>>>>>>>>>>>>>>>>>> failure >>>>>>>>>>>>>>>>>>>>>> on >>>>>>>>>>>>>>>>>>>>>>>>>>>> cursor iteration] >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.corruptedTreeException(BPlusTree.java:5927) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5438) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.next(BPlusTree.java:5661) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl$1.next(IgniteCacheOffheapManagerImpl.java:3020) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition$2.hasNextX(GridDhtLocalPartition.java:1226) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.doClear(GridDhtLocalPartition.java:1295) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition.clearTombstones(GridDhtLocalPartition.java:1242) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.distributed.dht.topology.PartitionsEvictManager$ClearTombstonesTask.run0(PartitionsEvictManager.java:673) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.distributed.dht.topology.PartitionsEvictManager$AbstractEvictionTask.run(PartitionsEvictManager.java:587) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7061) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>> java.lang.Thread.run(Thread.java:748) >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> Caused by: >>>>>>>> java.lang.AssertionError: >>>>>>>>> Key >>>>>>>>>>>> is not ready: >>>>>>>>>>>>>>>>>>>>>>>>>>>> CacheDataRowAdapter >>>>> [key=null, >>>>>>>>> val=null, >>>>>>>>>>>> expireTime=-1, >>>>>>>>>>>>>>>>>>>>>> ver=null, >>>>>>>>>>>>>>>>>>>>>>>>>>>> cacheId=0, >>>>>> link=0001003c000077d8] >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.key(CacheDataRowAdapter.java:837) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compare(CacheDataTree.java:382) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.tree.CacheDataTree.compare(CacheDataTree.java:63) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.compare(BPlusTree.java:5200) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.findLowerBound(BPlusTree.java:5317) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$ForwardCursor.fillFromBuffer0(BPlusTree.java:5588) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.fillFromBuffer(BPlusTree.java:5376) >>>>>>>>>>>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$AbstractForwardCursor.nextPage(BPlusTree.java:5428) >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://ci.ignite.apache.org/viewLog.html?buildId=4807946&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache9#testNameId1910487508546147692 >>>>>>>>>>>>>>>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://ci.ignite.apache.org/viewLog.html?buildId=4796925&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache9#testNameId7609674190425495190 >>>>>>>>>>>>>>>>>>>>>>>>>>>> [3] >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-11704 >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, 3 Dec 2019 at >>>> 13:39, >>>>>>> Alexei >>>>>>>>>>>> Scherbakov >>>>>>>>>>>>>>>>>>>>>>>>>>>> < >>>>> alexey.scherbak...@gmail.com> >>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Maxim, >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm not sure this is >>>>> purely a >>>>>>>>>>>> "tombstone" problem, >>>>>>>>>>>>>>>>>> could >>>>>>>>>>>>>>>>>>>> be >>>>>>>>>>>>>>>>>>>>>> a tree >>>>>>>>>>>>>>>>>>>>>>>>>>>>> concurrency issue. >>>>>>>>>>>>>>>>>>>>>>>>>>>>> Looks like the >>>>> investigation >>>>>> is >>>>>>>>>>> required. >>>>>>>>>>>>>>>>>>>>>>>>>>>>> For example, >> tombstone >>>>> logic >>>>>>> can >>>>>>>> be >>>>>>>>>>>> reverted but test >>>>>>>>>>>>>>>>>>>> logic >>>>>>>>>>>>>>>>>>>>>> is kept. >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> It seems Ivan Rakov >>>> already >>>>>>>>> suggested >>>>>>>>>>> to >>>>>>>>>>>> revert a >>>>>>>>>>>>>>>>>> commit >>>>>>>>>>>>>>>>>>>>>> from master >>>>>>>>>>>>>>>>>>>>>>>>>>>> branch >>>>>>>>>>>>>>>>>>>>>>>>>>>>> in another thread. >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>> пн, 2 дек. 2019 г. в >>>> 17:17, >>>>>>> Maxim >>>>>>>>>>>> Muzafarov < >>>>>>>>>>>>>>>>>>>>>> mmu...@apache.org>: >>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Igniters, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I've found a scary >>>> error >>>>>> [1] >>>>>>>> with >>>>>>>>>>>>>>>>>>>>> `CorruptedTreeException: >>>>>>>>>>>>>>>>>>>>>> B+Tree is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> corrupted` on TC in >>> the >>>>>>> master >>>>>>>>>>> branch. >>>>>>>>>>>> It seems >>>>>>>>>>>>>>>>>> that >>>>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>>>>>> issue is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> related to a [2] >>>>> tombstone >>>>>>>>>>>> implementation (probably >>>>>>>>>>>>>>>>>>>> not). >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Can anyone confirm >>> that >>>>> the >>>>>>>>> problem >>>>>>>>>>> is >>>>>>>>>>>> still >>>>>>>>>>>>>>>>>> actual? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If it is true, do >> we >>>> have >>>>>>> time >>>>>>>>> for >>>>>>>>>>>> resolving the >>>>>>>>>>>>>>>>>>>> problem? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Will it be better >> to >>>>> revert >>>>>>>> this >>>>>>>>>>>> commit from the >>>>>>>>>>>>>>>>>>>> release >>>>>>>>>>>>>>>>>>>>>> branch? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://ci.ignite.apache.org/viewLog.html?buildId=4796925&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_Cache9#testNameId7609674190425495190 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2] >>>>>>>>>>>>>>>>>> >>>>> https://issues.apache.org/jira/browse/IGNITE-11704 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Wed, 13 Nov 2019 >>> at >>>>>> 16:50, >>>>>>>>> Maxim >>>>>>>>>>>> Muzafarov < >>>>>>>>>>>>>>>>>>>>>> mmu...@apache.org> >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Igniters, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I've had >>>> conversations >>>>>> with >>>>>>>>> Nikolay >>>>>>>>>>>> and Alexey >>>>>>>>>>>>>>>>>> about >>>>>>>>>>>>>>>>>>>>>> working >>>>>>>>>>>>>>>>>>>>>>>>>>> progress >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [1] on ML, Spark, >>>>>>> Monitoring >>>>>>>>>>>> features which we >>>>>>>>>>>>>>>>>> are >>>>>>>>>>>>>>>>>>>>>> waiting for. It >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> seems the >> progress >>>>> dates >>>>>>> is a >>>>>>>>> bit >>>>>>>>>>>> slower than we >>>>>>>>>>>>>>>>>>>>>> expected earlier. >>>>>>>>>>>>>>>>>>>>>>>>>>>> I'd >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> suggest the >>> following >>>>>>> dates: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2 December - the >>>>> release >>>>>>>> branch >>>>>>>>>>>> cutting. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 30 December - >> code >>>>> freeze >>>>>>> of >>>>>>>>> the >>>>>>>>>>>> release branch >>>>>>>>>>>>>>>>>> (only >>>>>>>>>>>>>>>>>>>>>> blocker >>>>>>>>>>>>>>>>>>>>>>>>>>> issues >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> allowed) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 27 January 2020 - >>> the >>>>>>> voting >>>>>>>>> date >>>>>>>>>>>> (2+ weeks of >>>>>>>>>>>>>>>>>>>>>> stabilization >>>>>>>>>>>>>>>>>>>>>>>>>>> period) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Any objections? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Awatingfeaturescompletion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 7 Nov >> 2019 >>> at >>>>>>> 18:01, >>>>>>>>> Maxim >>>>>>>>>>>> Muzafarov < >>>>>>>>>>>>>>>>>>>>>> mmu...@apache.org> >>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Alexey, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Not yet. I will >>>>>> announce >>>>>>>> the >>>>>>>>>>>> release branch >>>>>>>>>>>>>>>>>> cutting >>>>>>>>>>>>>>>>>>>>>> stage with a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> separate post, >>>>>> probably, >>>>>>>> for >>>>>>>>> a >>>>>>>>>>> one >>>>>>>>>>>> week before >>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>>>>>> cut. No one >>>>>>>>>>>>>>>>>>>>>>>>>>> will >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> not miss it for >>>> sure. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Currently, all >>>> issues >>>>>> can >>>>>>>>> safely >>>>>>>>>>>> be pinned to >>>>>>>>>>>>>>>>>> 2.8 >>>>>>>>>>>>>>>>>>>>>> release, but >>>>>>>>>>>>>>>>>>>>>>>>>>> for >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> huge >>>> issues\features >>>>>>> (e.g. >>>>>>>>>>>> `baseline topology`, >>>>>>>>>>>>>>>>>>>>>> `persistence`) >>>>>>>>>>>>>>>>>>>>>>>>>>>> which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> are going to be >>>>>> included >>>>>>>>> into the >>>>>>>>>>>> release, it's >>>>>>>>>>>>>>>>>>>>> better >>>>>>>>>>>>>>>>>>>>>> to have a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> separate thread >>>>>>> discussion. >>>>>>>>> Do >>>>>>>>>>> you >>>>>>>>>>>> have such >>>>>>>>>>>>>>>>>> issues >>>>>>>>>>>>>>>>>>>>> in >>>>>>>>>>>>>>>>>>>>>> mind? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm trying to >>>>> estimate >>>>>>> new >>>>>>>>>>> release >>>>>>>>>>>> dates due >>>>>>>>>>>>>>>>>> to not >>>>>>>>>>>>>>>>>>>>>> all features >>>>>>>>>>>>>>>>>>>>>>>>>>>> which >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> we are waiting >>> for >>>>> [1] >>>>>>> will >>>>>>>>> be >>>>>>>>>>>> completed by >>>>>>>>>>>>>>>>>> the due >>>>>>>>>>>>>>>>>>>>>> dates >>>>>>>>>>>>>>>>>>>>>>>>>>> discussed >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'll back soon. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [1] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Awatingfeaturescompletion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Thu, 7 Nov >>> 2019 >>>> at >>>>>>>> 17:46, >>>>>>>>>>>> Alexey Goncharuk >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> < >>>>>>>> alexey.goncha...@gmail.com> >>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Maxim, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> A side note - >>> we >>>>> did >>>>>>> not >>>>>>>>> cut >>>>>>>>>>> the >>>>>>>>>>>> 2.8 branch >>>>>>>>>>>>>>>>>> yet, >>>>>>>>>>>>>>>>>>>>> did >>>>>>>>>>>>>>>>>>>>>> we? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> This >>> information >>>> is >>>>>> not >>>>>>>>>>>> reflected on the >>>>>>>>>>>>>>>>>> release >>>>>>>>>>>>>>>>>>>>>> page and I >>>>>>>>>>>>>>>>>>>>>>>>>>> just >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> realized >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that it is >> hard >>>> to >>>>>>> choose >>>>>>>>> a fix >>>>>>>>>>>> version for a >>>>>>>>>>>>>>>>>>>>> ticket >>>>>>>>>>>>>>>>>>>>>> that is >>>>>>>>>>>>>>>>>>>>>>>>>>>> being >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> merged >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> to master >> when >>>>>> release >>>>>>>>> scope is >>>>>>>>>>>> being >>>>>>>>>>>>>>>>>> finalized. >>>>>>>>>>>>>>>>>>>>>> This moment is >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> covered >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> neither in >> the >>>>>> release >>>>>>>>> process >>>>>>>>>>>> nor in the >>>>>>>>>>>>>>>>>>>>>> development process >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (unless I am >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> missing >>>> something). >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ср, 6 нояб. >>> 2019 >>>>> г. в >>>>>>>>> 13:55, >>>>>>>>>>>> Maxim Muzafarov >>>>>>>>>>>>>>>>>> < >>>>>>>>>>>>>>>>>>>>>>>>>>> mmu...@apache.org >>>>>>>>>>>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Igniters, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Ivan, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yes, it's >>> true >>>>> that >>>>>>>>>>> currently, >>>>>>>>>>>> all resolved >>>>>>>>>>>>>>>>>>>>> issues >>>>>>>>>>>>>>>>>>>>>> with 2.8 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> fixVersion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> will get >> into >>>> 2.8 >>>>>>>>> release. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Moreover, >>> I've >>>>>> marked >>>>>>>> all >>>>>>>>>>>> issues with empty >>>>>>>>>>>>>>>>>>>>>> fixVersion filed >>>>>>>>>>>>>>>>>>>>>>>>>>>> closed >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> since 2.7 >>> major >>>>>>> release >>>>>>>>> with >>>>>>>>>>>> 2.8 labels. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, 5 >> Nov >>>>> 2019 >>>>>> at >>>>>>>>> 15:03, >>>>>>>>>>>> Ivan >>>>>>>>>>>>>>>>>> Pavlukhin < >>>>>>>>>>>>>>>>>>>>>>>>>>>> vololo...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Maxim, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Could you >>>>> please >>>>>>>>> elaborate >>>>>>>>>>>> about a >>>>>>>>>>>>>>>>>> question >>>>>>>>>>>>>>>>>>>>> from >>>>>>>>>>>>>>>>>>>>>> Akash. >>>>>>>>>>>>>>>>>>>>>>>>>>> What >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> tickets >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> do we >>>> consider >>>>>> for >>>>>>>>> release? >>>>>>>>>>>> All with 2.8 >>>>>>>>>>>>>>>>>> fix >>>>>>>>>>>>>>>>>>>>>> version in >>>>>>>>>>>>>>>>>>>>>>>>>>> Jira >>>>>>>>>>>>>>>>>>>>>>>>>>>> or >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> there >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is a >>>> different >>>>>>>>> criteria? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> вт, 5 >> нояб. >>>>> 2019 >>>>>>> г. в >>>>>>>>>>> 15:01, >>>>>>>>>>>> Ivan >>>>>>>>>>>>>>>>>> Pavlukhin < >>>>>>>>>>>>>>>>>>>>>>>>>>>> vololo...@gmail.com >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Alexey, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> True. >> It >>> is >>>>>>>>> definitely to >>>>>>>>>>>> early for >>>>>>>>>>>>>>>>>>>> Calcite. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> вт, 5 >>> нояб. >>>>>> 2019 >>>>>>>> г. в >>>>>>>>>>>> 14:46, Alexey >>>>>>>>>>>>>>>>>>>> Zinoviev >>>>>>>>>>>>>>>>>>>>> < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> zaleslaw....@gmail.com >>>>> : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I >> have >>> no >>>>>>> ideas, >>>>>>>> I >>>>>>>>>>> think >>>>>>>>>>>> it's enough >>>>>>>>>>>>>>>>>> for >>>>>>>>>>>>>>>>>>>>>> this release. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> As I >>>>>> understand >>>>>>>>> it's >>>>>>>>>>> not >>>>>>>>>>>> the proper >>>>>>>>>>>>>>>>>> time >>>>>>>>>>>>>>>>>>>>> for >>>>>>>>>>>>>>>>>>>>>> Calcite >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> integration and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> so on, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> isn't >>> it >>>>>> @Igor >>>>>>>>>>>> Seliverstov? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> вт, 5 >>>> нояб. >>>>>>> 2019 >>>>>>>>> г. в >>>>>>>>>>>> 14:41, Maxim >>>>>>>>>>>>>>>>>>>>> Muzafarov >>>>>>>>>>>>>>>>>>>>>> < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> mmu...@apache.org >>> : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> Igniters, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Do >> we >>>>> want >>>>>> to >>>>>>>>> discuss >>>>>>>>>>>> something? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> What >>>> else >>>>>>>>> features do >>>>>>>>>>>> we want to >>>>>>>>>>>>>>>>>>>> include? >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If >>>> not, I >>>>>>>>> propose to >>>>>>>>>>>> exclude any >>>>>>>>>>>>>>>>>> other >>>>>>>>>>>>>>>>>>>>>> major features >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (except >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> already >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> discussed - >>>>>>> ML, >>>>>>>>>>>> Monitoring, Spark) >>>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>>>>>>> focus on bug >>>>>>>>>>>>>>>>>>>>>>>>>>>> fixing >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> and the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> master >>>>>> branch >>>>>>>>>>>> stabilization. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On >>> Wed, >>>>> 30 >>>>>>> Oct >>>>>>>>> 2019 >>>>>>>>>>> at >>>>>>>>>>>> 17:57, Akash >>>>>>>>>>>>>>>>>>>>> Shinde >>>>>>>>>>>>>>>>>>>>>> < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> akashshi...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> Because I >>>>>>>>> didn't >>>>>>>>>>> see >>>>>>>>>>>> it in this >>>>>>>>>>>>>>>>>> list >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Releaseissuesgroupedbystatus >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> Just >>>>>> wanted >>>>>>>> to >>>>>>>>> make >>>>>>>>>>>> sure its a >>>>>>>>>>>>>>>>>> part >>>>>>>>>>>>>>>>>>>> on >>>>>>>>>>>>>>>>>>>>>> 2.8. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> Thanks, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> Akash >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> On >>>> Wed, >>>>>> Oct >>>>>>>> 30, >>>>>>>>>>> 2019 >>>>>>>>>>>> at 8:20 PM >>>>>>>>>>>>>>>>>> Ivan >>>>>>>>>>>>>>>>>>>>>> Pavlukhin < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>> vololo...@gmail.com> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> Hi >>>>>> Akash, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> Why >>>>> do >>>>>>> you >>>>>>>>> think >>>>>>>>>>>> it is not >>>>>>>>>>>>>>>>>>>> included? >>>>>>>>>>>>>>>>>>>>> I >>>>>>>>>>>>>>>>>>>>>> see fix >>>>>>>>>>>>>>>>>>>>>>>>>>>> version >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2.8 in >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ticket >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> [1]. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> [1] >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-10884 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> ср, >>>>> 30 >>>>>>> окт. >>>>>>>>> 2019 >>>>>>>>>>>> г. в 17:29, >>>>>>>>>>>>>>>>>> Akash >>>>>>>>>>>>>>>>>>>>>> Shinde < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>> akashshi...@gmail.com >>>>>>>>> : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>> Hi, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>> Could >>>>>>>> you >>>>>>>>>>>> please include >>>>>>>>>>>>>>>>>>>>>> IGNITE-10884 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> < >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-10884> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> in 2.8 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> release. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> This >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> issue >>>>>>> is >>>>>>>>>>> blocker >>>>>>>>>>>> for me. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>> Thanks, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> Akash >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>> On >>>>>> Wed, >>>>>>>>> Oct 30, >>>>>>>>>>>> 2019 at 7:38 >>>>>>>>>>>>>>>>>> PM >>>>>>>>>>>>>>>>>>>>> Maxim >>>>>>>>>>>>>>>>>>>>>>>>>>> Muzafarov < >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> mmu...@apache.org> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> wrote: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>> Folks, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>> It >>>>>>>> seems >>>>>>>>> a >>>>>>>>>>>> week ago I've >>>>>>>>>>>>>>>>>>>> replied >>>>>>>>>>>>>>>>>>>>>> with the >>>>>>>>>>>>>>>>>>>>>>>>>>>> release >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> info >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> only to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> Artem. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>> Sorry >>>>>>>>> about >>>>>>>>>>>> that :-) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>> Here >>>>>>> is >>>>>>>>> what >>>>>>>>>>>> I've >>>>>>>>>>>>>>>>>> collected. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>> Let's >>>>>>>>>>> discuss! >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>> Igniters, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>> I've >>>>>>>>> prepared >>>>>>>>>>>> the Apache >>>>>>>>>>>>>>>>>> Ignite >>>>>>>>>>>>>>>>>>>>>> 2.8 release >>>>>>>>>>>>>>>>>>>>>>>>>>>> page >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [1] with >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the list >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>> known >>>>>>>>> issues >>>>>>>>>>>> which are >>>>>>>>>>>>>>>>>> related >>>>>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>>>>>>> 2.8 release >>>>>>>>>>>>>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> about the >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> additional >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>> release >>>>>>>>>>>> information. If >>>>>>>>>>>>>>>>>> I've >>>>>>>>>>>>>>>>>>>>> missed >>>>>>>>>>>>>>>>>>>>>>>>>>> something, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> please, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> feel free >> to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>> set >>>>>>>> `fix >>>>>>>>>>>> version` with >>>>>>>>>>>>>>>>>> `2.8`. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>> Details: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>> >>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> * >>>>>>>>> WAITING FOR >>>>>>>>>>>> COMPLETION * >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>> Here >>>>>>> is >>>>>>>>> the >>>>>>>>>>>> list of major >>>>>>>>>>>>>>>>>>>>> features >>>>>>>>>>>>>>>>>>>>>> which must >>>>>>>>>>>>>>>>>>>>>>>>>>>> be >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> completed >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> before >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>> creating >>>>>>>>> the >>>>>>>>>>>> release >>>>>>>>>>>>>>>>>> branch. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> - >>>>>>>> Apache >>>>>>>>>>>> ignite new >>>>>>>>>>>>>>>>>> monitoring >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> - >>>>>> ML >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> - >>>>>>> Spark >>>>>>>>> 2.4 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>> Details: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Awatingfeaturescompletion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> * >>>>>> TO >>>>>>>>> DISCUSS >>>>>>>>>>> * >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>> Previously >>>>>>>>>>>> some of the >>>>>>>>>>>>>>>>>> features >>>>>>>>>>>>>>>>>>>>>> were >>>>>>>>>>>>>>>>>>>>>>>>>>> mentioned >>>>>>>>>>>>>>>>>>>>>>>>>>>> but >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> discussion >>> not >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>> finalized yet >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> - >>>>>>>>> Automatic >>>>>>>>>>>> modules >>>>>>>>>>>>>>>>>> support for >>>>>>>>>>>>>>>>>>>>>> Apache >>>>>>>>>>>>>>>>>>>>>>>>>>> Ignite: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> find and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> resolve >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>> packages >>>>>>>>>>>> conflicts >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-11461 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> - >>>>>>>> Support >>>>>>>>>>> Java >>>>>>>>>>>> 11 for >>>>>>>>>>>>>>>>>> Apache >>>>>>>>>>>>>>>>>>>>> Ignite >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-11189 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> - >>>>>>>>> Callbacks >>>>>>>>>>>> from the >>>>>>>>>>>>>>>>>> striped >>>>>>>>>>>>>>>>>>>> pool >>>>>>>>>>>>>>>>>>>>>> due to >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> async/await may >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> hang a >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> cluster >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-12033 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> * >>>>>>> KNOWN >>>>>>>>>>> ISSUES >>>>>>>>>>>> * >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>> Bugs >>>>>>>> and >>>>>>>>>>>> features sorted by >>>>>>>>>>>>>>>>>>>>>> priority. If >>>>>>>>>>>>>>>>>>>>>>>>>>>> someone >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> knows any >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> additional >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>> information >>>>>>>>>>>> about any of >>>>>>>>>>>>>>>>>>>>> `blocker` >>>>>>>>>>>>>>>>>>>>>> issue, >>>>>>>>>>>>>>>>>>>>>>>>>>>> please, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> step in. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> - >>>>>>>> Unable >>>>>>>>> to >>>>>>>>>>>> use date as >>>>>>>>>>>>>>>>>> primary >>>>>>>>>>>>>>>>>>>>> key >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-8552 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> - >>>>>>>> Cluster >>>>>>>>>>>> hangs during >>>>>>>>>>>>>>>>>>>> concurrent >>>>>>>>>>>>>>>>>>>>>> node client >>>>>>>>>>>>>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> server >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> nodes >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> restart >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-9184 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>> Details: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolvedissues(notrelatedtodocumentation) >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>> >>>>> * >>>>>>>>>>>> DOCUMENTATION * >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> >>>>> The >>>>>>>> list >>>>>>>>> of >>>>>>>>>>>> issues\tasks >>>>>>>>>>>>>>>>>>>> related >>>>>>>>>>>>>>>>>>>>>> to Apache >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >>
