[GitHub] ignite pull request #3444: IGNITE-3999: Support case insensitive search in S...
GitHub user amirakhmedov opened a pull request: https://github.com/apache/ignite/pull/3444 IGNITE-3999: Support case insensitive search in SQL You can merge this pull request into a Git repository by running: $ git pull https://github.com/amirakhmedov/ignite IGNITE-3999 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3444.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3444 commit 71f5dde9673c2f6810db2125f788fa9eec335ba9 Author: Amir AkhmedovDate: 2018-01-29T04:52:48Z IGNITE-3999: Support case insensitive search in SQL ---
[GitHub] ignite pull request #3443: IGNITE-7090
GitHub user tonyschak opened a pull request: https://github.com/apache/ignite/pull/3443 IGNITE-7090 Fixed Broken Semaphore by checking state on creation of new on. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tonyschak/ignite IGNITE-7090-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3443.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3443 commit c30592f94d2d30f7ec9702ccd878f17121f328ad Author: Tim OnyschakDate: 2017-10-26T18:55:42Z IGNITE-6767 reset of the topVer on loading of the entry. commit 0014171e045bc993fbcaf7279378294fee44810f Author: Tim Onyschak Date: 2017-12-04T20:05:37Z Revert "IGNITE-6767 reset of the topVer on loading of the entry." This reverts commit c30592f94d2d30f7ec9702ccd878f17121f328ad. commit a4469e17f8097ab58d157095de075f9593cdab6c Author: Tim Onyschak Date: 2017-12-04T20:12:55Z done Merge branch 'master' of https://github.com/apache/ignite commit d75a9b5ffc71f157a744c7f68bc224fd5a86137c Author: Tim Onyschak Date: 2018-01-29T02:00:44Z Merge branch 'master-true' into IGNITE-7090-1 * master-true: Revert "IGNITE-6767 reset of the topVer on loading of the entry." IGNITE-6767 reset of the topVer on loading of the entry. commit 3de65e55f2186529b281389029414daeb651f357 Author: Tim Onyschak Date: 2018-01-29T02:20:21Z Added Cluster State check for Semaphore State check commit dde908ffa9e358810d1ad618b9cdf2b697c742b7 Author: Tim Onyschak Date: 2018-01-29T02:21:20Z Merge branch 'master-up' into IGNITE-7090-1 * master-up: (27 commits) IGNITE-7550 Fix windows *.bat scripts Java 9 compatibility IGNITE-7003: Fixed SQL WAL enable/disable command usability: throw exception in case of change failure. IGNITE-7031 Web Console: Refactored confirmation cancellation logic. IGNITE-7521 Add new assertions to FilePageStore and provide page content if read page is broken - Fixes #3432. IGNITE-7530 .NET: Fix GetAll memory usage and performance in binary mode IGNITE-7392 Visor Cmd: Added missing word 'factory'. IGNITE-7064 Web Console: Minor test fix. Revert "IGNITE-7514 Choose owner primary node after cluster restart" IGNITE-7529 Web Console: Refactor UIGrid column filters. IGNITE-7522 Web Console: Fixed cluster selector state after cluster restart. IGNITE-7316: Make Linear SVM for binary classification ignite-6643 Marshalling improvements IGNITE-7064 Web Console: Implemented basic E2E tests. IGNITE-7502 Disabled BLT for non-persistent caches AI 2.4 release notes. IGNITE-7507: Ignite node performance drop during checkpoint start: store metapage eviction causes long checkpoint lock hold time - Fixes #3423. IGNITE-7506 Fixed resetting of GridClusterStateProcessor#compatibilityMode flag IGNITE-6832 Properly handle IO errors while checkpointing - Fixes #3394. IGNITE-7514 Choose owner primary node after cluster restart IGNITE-7443: Native batching for ODBC. This closes #3422. ... commit 729e1112cdc522065a2d9a52b6ad47e603e96430 Author: Tim Onyschak Date: 2018-01-29T02:28:28Z Added to test suite commit f0fbbc35989bb7678b7df3902fbebdbe26517a27 Author: Tim Onyschak Date: 2018-01-29T03:28:39Z fixed placement of call ---
Re: Ignite Semaphore Bug 7090
Jira Username: Timay On Sat, Jan 27, 2018 at 1:43 AM, Dmitriy Setrakyanwrote: > Tim, can you please send your Apache Jira ID here, so I could add you as > Ignite contributor? > > On Thu, Jan 25, 2018 at 6:02 PM, Tim Onyschak wrote: > >> It does not look like i have permissions to assign tickets. I'll gladly >> take it, if somebody can assign it to me. >> >> Also, Vlad i updated the ticket with my comment as well. >> >> >> On Thu, Jan 25, 2018 at 7:44 PM, Yakov Zhdanov >> wrote: >> >> > Vlad and Tim, thanks for working on this! >> > >> > Tim, please assign ticket to yourself to follow community process. >> > Currently I see it is unassigned. >> > >> > --Yakov >> > >> > 2018-01-25 8:53 GMT-08:00 Vladisav Jelisavcic : >> > >> >> Hi Tim, >> >> >> >> thank you for delving deeper into the problem, >> >> I left you a comment/question on the JIRA. >> >> >> >> Best regards, >> >> Vladisav >> >> >> >> On Tue, Jan 23, 2018 at 3:00 PM, Vladisav Jelisavcic < >> vladis...@gmail.com >> >> > >> >> wrote: >> >> >> >> > Hi Tim, >> >> > >> >> > thanks for the update! I left you a comment on Jira. >> >> > >> >> > Best regards, >> >> > Vladisav >> >> > >> >> > On Mon, Jan 22, 2018 at 6:17 PM, Tim Onyschak >> >> wrote: >> >> > >> >> >> Hey Vladisav, >> >> >> >> >> >> I implemented your requests. Take a look, specifically, i created an >> >> >> interface to encapsulate the NodeUpdates and let >> >> >> the DataStructuresProcessor handle the execution by checking for one >> >> type >> >> >> as opposed to multiple if checks. In this case it checks for >> >> GridCacheNodeUpdate >> >> >> instance and executes onNodeRemoved. Let me know what you think. >> >> >> >> >> >> Thanks, >> >> >> Tim >> >> >> >> >> >> >> >> >> >> >> >> On Sat, Jan 20, 2018 at 8:10 AM, Vladisav Jelisavcic < >> >> vladis...@gmail.com >> >> >> > wrote: >> >> >> >> >> >>> Hi Tim, >> >> >>> >> >> >>> I reviewed your contribution and left you some comments on the pr. >> >> >>> Thanks! >> >> >>> >> >> >>> Vladisav >> >> >>> >> >> >>> On Wed, Jan 17, 2018 at 10:14 PM, Vladisav Jelisavcic < >> >> >>> vladis...@gmail.com> wrote: >> >> >>> >> >> Hi Tim, >> >> >> >> thank you for the contribution! >> >> I'll do the review soon and let you know. >> >> >> >> >> >> >> >> On Wed, Jan 17, 2018 at 8:56 AM, Yakov Zhdanov < >> yzhda...@apache.org> >> >> wrote: >> >> >> >> > Thanks Tim! I hope Vlad can review your patch. If this does not >> >> happen >> >> > in >> >> > 2-3 days I will take a look. Can you please let me know on >> weekend >> >> if I >> >> > need to? >> >> > >> >> > --Yakov >> >> > >> >> > 2018-01-16 23:36 GMT+03:00 Tim Onyschak : >> >> > >> >> > > Hey all, >> >> > > >> >> > > I created a patch and posted to user group, was told feed back >> >> would >> >> > be >> >> > > left on the jira. I wanted to see if we could get a fix in with >> >> 2.4, >> >> > could >> >> > > somebody please review. >> >> > > >> >> > > http://apache-ignite-users.70518.x6.nabble.com/Semaphore- >> >> > > Stuck-when-no-acquirers-to-assign-permit-td18639.html >> >> > > >> >> > > https://issues.apache.org/jira/browse/IGNITE-7090 >> >> > > >> >> > > https://github.com/apache/ignite/pull/3138 >> >> > > >> >> > > Thanks, >> >> > > Tim >> >> > > >> >> > >> >> >> >> >> >> >>> >> >> >> >> >> > >> >> >> > >> > >> > >