[jira] [Created] (IGNITE-4069) Web console: error triangle icon is not displayed for some fields
Pavel Konstantinov created IGNITE-4069: -- Summary: Web console: error triangle icon is not displayed for some fields Key: IGNITE-4069 URL: https://issues.apache.org/jira/browse/IGNITE-4069 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Priority: Minor For example this can be reproduced on CollisionSPI fields for case FIFO. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4069) Web console: error triangle icon is not displayed for some fields
[ https://issues.apache.org/jira/browse/IGNITE-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-4069: --- Description: For example this can be reproduced on CollisionSPI fields for case FIFO. To reproduce enter the value '-0' - the field shows red frame but red triangle is not displayed. was:For example this can be reproduced on CollisionSPI fields for case FIFO. > Web console: error triangle icon is not displayed for some fields > - > > Key: IGNITE-4069 > URL: https://issues.apache.org/jira/browse/IGNITE-4069 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > > For example this can be reproduced on CollisionSPI fields for case FIFO. > To reproduce enter the value '-0' - the field shows red frame but red > triangle is not displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4048) Web console: result panel is not displayed in case if first query is incorrect
[ https://issues.apache.org/jira/browse/IGNITE-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov resolved IGNITE-4048. Resolution: Fixed Assignee: Pavel Konstantinov Fixed. Pavel, please test. > Web console: result panel is not displayed in case if first query is incorrect > -- > > Key: IGNITE-4048 > URL: https://issues.apache.org/jira/browse/IGNITE-4048 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov > > Create a new Query > Write 'select * from qwerty' > Execute > Observed: there is no result panel with error message below the query area. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571506#comment-15571506 ] Pavel Tupitsyn commented on IGNITE-1915: 1,2,3) Done > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3731) Web Console: Add fetch first page only for query on SQL screen
[ https://issues.apache.org/jira/browse/IGNITE-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov resolved IGNITE-3731. Resolution: Fixed Assignee: Vasiliy Sisko (was: Andrey Novikov) Fixed. Vasiliy, please test. > Web Console: Add fetch first page only for query on SQL screen > -- > > Key: IGNITE-3731 > URL: https://issues.apache.org/jira/browse/IGNITE-3731 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Vasiliy Sisko >Priority: Minor > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4070) .NET: Introduce transformers to SCAN queries
Pavel Tupitsyn created IGNITE-4070: -- Summary: .NET: Introduce transformers to SCAN queries Key: IGNITE-4070 URL: https://issues.apache.org/jira/browse/IGNITE-4070 Project: Ignite Issue Type: New Feature Components: platforms Reporter: Pavel Tupitsyn Fix For: 1.8 Same thing in .NET as IGNITE-2546. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4059) Web console: Error in log on break of animation.
[ https://issues.apache.org/jira/browse/IGNITE-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-4059: -- Assignee: Andrey Novikov > Web console: Error in log on break of animation. > > > Key: IGNITE-4059 > URL: https://issues.apache.org/jira/browse/IGNITE-4059 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Andrey Novikov > Fix For: 1.8 > > > angular.js:13920 TypeError: Cannot read property 'on' of null > at Object.TooltipFactoryDecorated.config.onShow (tooltip.js:31) > at enterAnimateCallback (angular-strap.js:553) > at processQueue (angular.js:16383) > at angular.js:16399 > at Scope.$eval (angular.js:17682) > at Scope.$digest (angular.js:17495) > at Scope.$apply (angular.js:17790) > at HTMLElement. (angular.js:25890) > at HTMLElement.dispatch (jquery.js:5201) > at HTMLElement.elemData.handle (jquery.js:5009) > To reproduce: > # F.e. add some type in Type configurations table on Binary configuration > section of cluster. > # Remove added type by click on "X" button when tooltip show animation in > progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4059) Web console: Error in log on break of animation.
[ https://issues.apache.org/jira/browse/IGNITE-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-4059: - Assignee: Vasiliy Sisko (was: Andrey Novikov) > Web console: Error in log on break of animation. > > > Key: IGNITE-4059 > URL: https://issues.apache.org/jira/browse/IGNITE-4059 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko > Fix For: 1.8 > > > angular.js:13920 TypeError: Cannot read property 'on' of null > at Object.TooltipFactoryDecorated.config.onShow (tooltip.js:31) > at enterAnimateCallback (angular-strap.js:553) > at processQueue (angular.js:16383) > at angular.js:16399 > at Scope.$eval (angular.js:17682) > at Scope.$digest (angular.js:17495) > at Scope.$apply (angular.js:17790) > at HTMLElement. (angular.js:25890) > at HTMLElement.dispatch (jquery.js:5201) > at HTMLElement.elemData.handle (jquery.js:5009) > To reproduce: > # F.e. add some type in Type configurations table on Binary configuration > section of cluster. > # Remove added type by click on "X" button when tooltip show animation in > progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4059) Web console: Error in log on break of animation.
[ https://issues.apache.org/jira/browse/IGNITE-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571521#comment-15571521 ] Andrey Novikov commented on IGNITE-4059: Fixed. Vasiliy, please test. > Web console: Error in log on break of animation. > > > Key: IGNITE-4059 > URL: https://issues.apache.org/jira/browse/IGNITE-4059 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko > Fix For: 1.8 > > > angular.js:13920 TypeError: Cannot read property 'on' of null > at Object.TooltipFactoryDecorated.config.onShow (tooltip.js:31) > at enterAnimateCallback (angular-strap.js:553) > at processQueue (angular.js:16383) > at angular.js:16399 > at Scope.$eval (angular.js:17682) > at Scope.$digest (angular.js:17495) > at Scope.$apply (angular.js:17790) > at HTMLElement. (angular.js:25890) > at HTMLElement.dispatch (jquery.js:5201) > at HTMLElement.elemData.handle (jquery.js:5009) > To reproduce: > # F.e. add some type in Type configurations table on Binary configuration > section of cluster. > # Remove added type by click on "X" button when tooltip show animation in > progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4059) Web console: Error in log on break of animation.
[ https://issues.apache.org/jira/browse/IGNITE-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov resolved IGNITE-4059. Resolution: Fixed > Web console: Error in log on break of animation. > > > Key: IGNITE-4059 > URL: https://issues.apache.org/jira/browse/IGNITE-4059 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko > Fix For: 1.8 > > > angular.js:13920 TypeError: Cannot read property 'on' of null > at Object.TooltipFactoryDecorated.config.onShow (tooltip.js:31) > at enterAnimateCallback (angular-strap.js:553) > at processQueue (angular.js:16383) > at angular.js:16399 > at Scope.$eval (angular.js:17682) > at Scope.$digest (angular.js:17495) > at Scope.$apply (angular.js:17790) > at HTMLElement. (angular.js:25890) > at HTMLElement.dispatch (jquery.js:5201) > at HTMLElement.elemData.handle (jquery.js:5009) > To reproduce: > # F.e. add some type in Type configurations table on Binary configuration > section of cluster. > # Remove added type by click on "X" button when tooltip show animation in > progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4051) Web console: Dropdown menu is closed on move to tooltip with long variant value.
[ https://issues.apache.org/jira/browse/IGNITE-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-4051: -- Assignee: Andrey Novikov > Web console: Dropdown menu is closed on move to tooltip with long variant > value. > > > Key: IGNITE-4051 > URL: https://issues.apache.org/jira/browse/IGNITE-4051 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Andrey Novikov > Fix For: 1.8 > > > # Open dropdown with long values. > # Move mouse to long value with '...' in end. > # Move mouse to showed tooltip for value. > Dropdown menu is closed when mouse cursor enter on area of tooltip. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4051) Web console: Dropdown menu is closed on move to tooltip with long variant value.
[ https://issues.apache.org/jira/browse/IGNITE-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov resolved IGNITE-4051. Resolution: Fixed Fixed. Vasiliy, please test. > Web console: Dropdown menu is closed on move to tooltip with long variant > value. > > > Key: IGNITE-4051 > URL: https://issues.apache.org/jira/browse/IGNITE-4051 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Andrey Novikov > Fix For: 1.8 > > > # Open dropdown with long values. > # Move mouse to long value with '...' in end. > # Move mouse to showed tooltip for value. > Dropdown menu is closed when mouse cursor enter on area of tooltip. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4059) Web console: Error in log on break of animation.
[ https://issues.apache.org/jira/browse/IGNITE-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571531#comment-15571531 ] Vasiliy Sisko commented on IGNITE-4059: --- Tested > Web console: Error in log on break of animation. > > > Key: IGNITE-4059 > URL: https://issues.apache.org/jira/browse/IGNITE-4059 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko > Fix For: 1.8 > > > angular.js:13920 TypeError: Cannot read property 'on' of null > at Object.TooltipFactoryDecorated.config.onShow (tooltip.js:31) > at enterAnimateCallback (angular-strap.js:553) > at processQueue (angular.js:16383) > at angular.js:16399 > at Scope.$eval (angular.js:17682) > at Scope.$digest (angular.js:17495) > at Scope.$apply (angular.js:17790) > at HTMLElement. (angular.js:25890) > at HTMLElement.dispatch (jquery.js:5201) > at HTMLElement.elemData.handle (jquery.js:5009) > To reproduce: > # F.e. add some type in Type configurations table on Binary configuration > section of cluster. > # Remove added type by click on "X" button when tooltip show animation in > progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-4059) Web console: Error in log on break of animation.
[ https://issues.apache.org/jira/browse/IGNITE-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko closed IGNITE-4059. - Assignee: (was: Vasiliy Sisko) > Web console: Error in log on break of animation. > > > Key: IGNITE-4059 > URL: https://issues.apache.org/jira/browse/IGNITE-4059 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko > Fix For: 1.8 > > > angular.js:13920 TypeError: Cannot read property 'on' of null > at Object.TooltipFactoryDecorated.config.onShow (tooltip.js:31) > at enterAnimateCallback (angular-strap.js:553) > at processQueue (angular.js:16383) > at angular.js:16399 > at Scope.$eval (angular.js:17682) > at Scope.$digest (angular.js:17495) > at Scope.$apply (angular.js:17790) > at HTMLElement. (angular.js:25890) > at HTMLElement.dispatch (jquery.js:5201) > at HTMLElement.elemData.handle (jquery.js:5009) > To reproduce: > # F.e. add some type in Type configurations table on Binary configuration > section of cluster. > # Remove added type by click on "X" button when tooltip show animation in > progress. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3617) Implement support for "Local node" mode on SQL screen
[ https://issues.apache.org/jira/browse/IGNITE-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov updated IGNITE-3617: --- Description: It will be useful to have "Local node" check box and dialog for selecting node. This mode should be implemented for: execute, scan. was: It will be useful to have "Local node" check box and dialog for selecting node. This mode should be implemented for: execute, explain, scan. > Implement support for "Local node" mode on SQL screen > - > > Key: IGNITE-3617 > URL: https://issues.apache.org/jira/browse/IGNITE-3617 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Kuznetsov > Fix For: 1.8 > > > It will be useful to have "Local node" check box and dialog for selecting > node. > This mode should be implemented for: execute, scan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3617) Implement support for "Local node" mode on SQL screen
[ https://issues.apache.org/jira/browse/IGNITE-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-3617: -- Assignee: Andrey Novikov > Implement support for "Local node" mode on SQL screen > - > > Key: IGNITE-3617 > URL: https://issues.apache.org/jira/browse/IGNITE-3617 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Andrey Novikov > Fix For: 1.8 > > > It will be useful to have "Local node" check box and dialog for selecting > node. > This mode should be implemented for: execute, scan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3731) Web Console: Add fetch first page only for query on SQL screen
[ https://issues.apache.org/jira/browse/IGNITE-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko reassigned IGNITE-3731: - Assignee: Pavel Konstantinov (was: Vasiliy Sisko) > Web Console: Add fetch first page only for query on SQL screen > -- > > Key: IGNITE-3731 > URL: https://issues.apache.org/jira/browse/IGNITE-3731 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3617) Implement support for "Local node" mode on SQL screen
[ https://issues.apache.org/jira/browse/IGNITE-3617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov resolved IGNITE-3617. Resolution: Fixed Implemented. Pavel, please test. > Implement support for "Local node" mode on SQL screen > - > > Key: IGNITE-3617 > URL: https://issues.apache.org/jira/browse/IGNITE-3617 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Andrey Novikov > Fix For: 1.8 > > > It will be useful to have "Local node" check box and dialog for selecting > node. > This mode should be implemented for: execute, scan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4071) Web console: Focus lost from key type on input.
Vasiliy Sisko created IGNITE-4071: - Summary: Web console: Focus lost from key type on input. Key: IGNITE-4071 URL: https://issues.apache.org/jira/browse/IGNITE-4071 Project: Ignite Issue Type: Bug Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko Assignee: Maxim Afanasiev Fix For: 1.8 On model page: # Uncheck "Generate POJO classes" checkbox. # Try to input into "Key type" field. After every input field lost focus. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4072) Web console: Disable Anotation variant of "Query metadata" when POJO is disabled.
Vasiliy Sisko created IGNITE-4072: - Summary: Web console: Disable Anotation variant of "Query metadata" when POJO is disabled. Key: IGNITE-4072 URL: https://issues.apache.org/jira/browse/IGNITE-4072 Project: Ignite Issue Type: Bug Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko Fix For: 1.8 On model page: # Uncheck "Generate POJO classes" # Select Anotation variant of "Query metadata" field. # Input invalid java class names in "Key type" and "Value type" fields. # Switch preview generation to Java. Generated code is invalid and should not be possible. cache.setIndexedTypes( 6adved.class, WRONG_NAME.class ); -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1915) .NET: Ignite as Entity Framework Second-Level Cache
[ https://issues.apache.org/jira/browse/IGNITE-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571506#comment-15571506 ] Pavel Tupitsyn edited comment on IGNITE-1915 at 10/13/16 11:13 AM: --- Done was (Author: ptupitsyn): 1,2,3) Done > .NET: Ignite as Entity Framework Second-Level Cache > --- > > Key: IGNITE-1915 > URL: https://issues.apache.org/jira/browse/IGNITE-1915 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .net, roadmap > Fix For: 1.8 > > > Entity Framework is #1 ORM for .NET > We should provide easy solution to boost Entity Framework performance with > Ignite. > EF5 and EF6 have different 2nd level cache mechanisms (EF5 has a built-in > one, EF6 requies more customization or a 3rd party lib like > https://efcache.codeplex.com/). For now, let's do EF6 only. > This should be in a separate assembly and a separate NuGet package. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4073) OFFHEAP cache context isOffHeapEnabled return false
Andrew Mashenkov created IGNITE-4073: Summary: OFFHEAP cache context isOffHeapEnabled return false Key: IGNITE-4073 URL: https://issues.apache.org/jira/browse/IGNITE-4073 Project: Ignite Issue Type: Bug Components: cache Reporter: Andrew Mashenkov Priority: Critical Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. I't seems to be a bug, because, really, entries are put to off-heap. Due to this bug, TtlManager could not correctly evict expired entries that can result in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4073) OFFHEAP cache context isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reassigned IGNITE-4073: Assignee: Andrew Mashenkov > OFFHEAP cache context isOffHeapEnabled return false > --- > > Key: IGNITE-4073 > URL: https://issues.apache.org/jira/browse/IGNITE-4073 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > > Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return > false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. > I't seems to be a bug, because, really, entries are put to off-heap. > Due to this bug, TtlManager could not correctly evict expired entries that > can result in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4073) OFFHEAP cache context isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571672#comment-15571672 ] ASF GitHub Bot commented on IGNITE-4073: GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1158 IGNITE-4073: OFFHEAP cache context method isOffHeapEnabled() return false You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4073 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1158.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 #1158 commit c7eed8859202b99cc64b7f6d6efe46acf71ad72a Author: Denis Magda Date: 2016-07-13T11:19:51Z IGNITE-3440: Ignite Services: ServiceTopologyCallable is executed before system cache is started (cherry picked from commit 06b24a9) commit 2b5067b528bf6442450b0c16d0bfb1437ea41e1a Author: Denis Magda Date: 2016-07-15T06:35:41Z IgniteDataStreamer: fixed JavaDoc (cherry picked from commit 2537e0f) commit 89fd76fa2e85cfa1c06fbd5151086f958aefa685 Author: Andrey Novikov Date: 2016-07-15T09:54:21Z IGNITE-3446 Visor CMD: improve usability for batch mode. (cherry picked from commit 4897315) commit 2f78346e0e3d6a1cb9483b66144175c826a1ff5f Author: sboikov Date: 2016-07-01T09:16:56Z ignite-1088 Implemented store for multi jvm tests (cherry picked from commit f91b699) commit ade57eaf5b77f779642be424d8cdf858a327ce2d Author: sboikov Date: 2016-07-05T04:43:51Z ignite-1088 Implemented store for multi jvm tests (fixed NPE) (cherry picked from commit d31a476) commit d2198a1df0e5c907434ec1a465eb118823723439 Author: sboikov Date: 2016-07-04T18:08:24Z ignite-1089 Fixed tests for multi jvm mode. This closes #846. (cherry picked from commit bf57413) commit a648e88c14295bf2c45b8e200eb5a3137997e131 Author: sboikov Date: 2016-07-15T13:26:00Z ignite-1089 Fixed tests for multi jvm mode. This closes #846. (cherry picked from commit bf57413) commit 8d6273780bdb63397dfddaf7b7c1e65a8b717e8d Author: sboikov Date: 2016-07-15T13:40:31Z Added more info in assert message. commit 4f97444c1e6ac29648dd96bc93f878e1d2c3e784 Author: Denis Magda Date: 2016-07-18T12:21:46Z IGNITE-3455: Entry placed on C++ side is not found on Java side (cherry picked from commit 84e83c9) commit e1195296ddc883c0a980f64bf0d80c26ef78b233 Author: sboikov Date: 2016-07-13T09:29:33Z ignite-3392 Added test. (cherry picked from commit a056954) commit 46f42723ac76c025863d7a9250de3eec1eca524a Author: sboikov Date: 2016-07-13T09:41:18Z ignite-3413 Use cache node filter for continuous query registration (cherry picked from commit 89d64e7) commit 590dffbe47d015db36710ba7708fd7d83269329f Author: sboikov Date: 2016-07-19T10:35:59Z ignite-3465 Do not call super.toString for not-initialized BinaryObjectImpl. (cherry picked from commit 78d7c13) commit 279de8f7c51dc93480bf64231321c451c7c11780 Author: vozerov-gridgain Date: 2016-07-19T12:54:27Z IGNITE-3416: CPP: Fixed string deserialization performance issue. commit 1dc8bcc20d89eb4172c4b1c8f718419f059c6cc2 Author: vozerov-gridgain Date: 2016-07-19T12:16:21Z IGNITE-3414: Hadoop: implemented new weight-based map-reduce planner. commit ecc77b0180b3b16303988e1dc187b53e7b96a111 Author: vozerov-gridgain Date: 2016-07-19T13:09:06Z IGNITE-3414: Hadoop: implemented new weight-based map-reduce planner. commit 51add5049c9603a143a1a8f9233d94f92c8394da Author: Pavel Tupitsyn Date: 2016-07-19T14:11:46Z IGNITE-3511: .NET: Fixed AffinityFunctionBase.cs placement, added missing Package-Info.cs files. commit 5ec99e8d987d7c966a55b8138aade6643decd5dd Author: Valentin Kulichenko Date: 2016-07-19T23:01:32Z IGNITE-3470 - Support EXPIRED events in continuous queries commit d767e518bf7844e3dcdb3f3fdc02da5ecc1b4f54 Author: Valentin Kulichenko Date: 2016-07-07T07:05:16Z Revert IGNITE-2949 due to broken compatibility commit 7140ee9ded458e5aedd1c5a9852204337fc3 Author: Valentin Kulichenko Date: 2016-07-19T23:23:27Z Revert IGNITE-2949 due to broken compatibility commit 6b8020d3ffef55039d0afa55ed5925d9fdb914d2 Author: Sergi Vladykin Date: 2016-07-13T17:19:25Z ignite-3254 - fixed (cherry picked from commit 4d2be72) commit 11c7e8fe53461f84924e5c29893865191f236c8c Author: Anton Vinogradov Date: 2016-07-20T08:31:14Z Documentation fix commit 9b55658749d0e2a869bbb3614034d8aa1f0e95c1 Author: vozerov-gridgain Date: 2016-07-20T11:14:50Z IGNITE-3405: IGFS: Restricted path modes interleaving, so that now only DUAL -> PRIMARY and DUAL -> PROXY paths are possible. commit 6c5218f4d67c8e247f59dbe8de
[jira] [Updated] (IGNITE-4073) OFFHEAP cache context isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4073: - Description: Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. I't seems to be a bug, because, really, entries are put to off-heap. Due to this bug, TtlManager could not correctly evict expired entries that can results in OOME. was: Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. I't seems to be a bug, because, really, entries are put to off-heap. Due to this bug, TtlManager could not correctly evict expired entries that can result in OOME. > OFFHEAP cache context isOffHeapEnabled return false > --- > > Key: IGNITE-4073 > URL: https://issues.apache.org/jira/browse/IGNITE-4073 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: Semen Boikov >Priority: Critical > > Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return > false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. > I't seems to be a bug, because, really, entries are put to off-heap. > Due to this bug, TtlManager could not correctly evict expired entries that > can results in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4073) OFFHEAP cache context isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4073: - Assignee: Semen Boikov (was: Andrew Mashenkov) > OFFHEAP cache context isOffHeapEnabled return false > --- > > Key: IGNITE-4073 > URL: https://issues.apache.org/jira/browse/IGNITE-4073 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: Semen Boikov >Priority: Critical > > Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return > false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. > I't seems to be a bug, because, really, entries are put to off-heap. > Due to this bug, TtlManager could not correctly evict expired entries that > can result in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4073) OFFHEAP cache context method isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4073: - Summary: OFFHEAP cache context method isOffHeapEnabled return false (was: OFFHEAP cache context isOffHeapEnabled return false) > OFFHEAP cache context method isOffHeapEnabled return false > -- > > Key: IGNITE-4073 > URL: https://issues.apache.org/jira/browse/IGNITE-4073 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: Semen Boikov >Priority: Critical > > Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return > false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. > I't seems to be a bug, because, really, entries are put to off-heap. > Due to this bug, TtlManager could not correctly evict expired entries that > can results in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-4073) OFFHEAP cache context method isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov closed IGNITE-4073. Bug in TtlManager > OFFHEAP cache context method isOffHeapEnabled return false > -- > > Key: IGNITE-4073 > URL: https://issues.apache.org/jira/browse/IGNITE-4073 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > > Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return > false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. > I't seems to be a bug, because, really, entries are put to off-heap. > Due to this bug, TtlManager could not correctly evict expired entries that > can results in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4054) Add debug to trace HadoopMapReducePlanner results.
[ https://issues.apache.org/jira/browse/IGNITE-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-4054: Assignee: Taras Ledkov (was: Vladimir Ozerov) > Add debug to trace HadoopMapReducePlanner results. > -- > > Key: IGNITE-4054 > URL: https://issues.apache.org/jira/browse/IGNITE-4054 > Project: Ignite > Issue Type: Task > Components: hadoop >Affects Versions: 1.7 >Reporter: Vladimir Ozerov >Assignee: Taras Ledkov >Priority: Minor > Fix For: 1.8 > > > This is necessary to track planning process. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3640) IGFS: Local secondary: Investigate whether we need BufferedInputStream for open operation.
[
https://issues.apache.org/jira/browse/IGNITE-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov reassigned IGNITE-3640:
Assignee: Taras Ledkov
> IGFS: Local secondary: Investigate whether we need BufferedInputStream for
> open operation.
> --
>
> Key: IGNITE-3640
> URL: https://issues.apache.org/jira/browse/IGNITE-3640
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> We need to accurately investigate IGFS input stream workflow. I have doubts
> we really need to extend from {{BufferedInputStream}} here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-3664) IGFS: Local secondary: Support blockSize attribute
[ https://issues.apache.org/jira/browse/IGNITE-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov reassigned IGNITE-3664: Assignee: Taras Ledkov > IGFS: Local secondary: Support blockSize attribute > -- > > Key: IGNITE-3664 > URL: https://issues.apache.org/jira/browse/IGNITE-3664 > Project: Ignite > Issue Type: Task > Components: IGFS >Reporter: Taras Ledkov >Assignee: Taras Ledkov > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-3643) IGFS: Local secondary: Define proper default buffer size.
[
https://issues.apache.org/jira/browse/IGNITE-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov reassigned IGNITE-3643:
Assignee: Taras Ledkov
> IGFS: Local secondary: Define proper default buffer size.
> -
>
> Key: IGNITE-3643
> URL: https://issues.apache.org/jira/browse/IGNITE-3643
> Project: Ignite
> Issue Type: Task
> Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 1.8
>
>
> If we decide to leave buffers for streams, we need to agree on a proper
> default for it. Currently it is {{8Kb}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-4030) Streamline PlatformTarget interface
[ https://issues.apache.org/jira/browse/IGNITE-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571915#comment-15571915 ] Pavel Tupitsyn commented on IGNITE-4030: Further considerations: * Allocating a stream when it is not used is unacceptable * Allocating a stream for a single primitive (bool, int, long, etc) is unacceptable > Streamline PlatformTarget interface > --- > > Key: IGNITE-4030 > URL: https://issues.apache.org/jira/browse/IGNITE-4030 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > 1) Review the set of inOut methods. There should be one uber-method which > takes a stream and an object, returns a stream and an object. This method > covers all use cases. Other methods should gradually simplify the signature. > 2) Provide a symmetrical callback method set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4030) Streamline PlatformTarget interface
[ https://issues.apache.org/jira/browse/IGNITE-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571915#comment-15571915 ] Pavel Tupitsyn edited comment on IGNITE-4030 at 10/13/16 2:31 PM: -- Further considerations: * Allocating a stream when it is not used is unacceptable. This is solved in inObjectStreamOutObjectStream. * Allocating a stream for a single primitive (bool, int, long, etc) is unacceptable. So InStreamOutLong should stay. was (Author: ptupitsyn): Further considerations: * Allocating a stream when it is not used is unacceptable * Allocating a stream for a single primitive (bool, int, long, etc) is unacceptable > Streamline PlatformTarget interface > --- > > Key: IGNITE-4030 > URL: https://issues.apache.org/jira/browse/IGNITE-4030 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > 1) Review the set of inOut methods. There should be one uber-method which > takes a stream and an object, returns a stream and an object. This method > covers all use cases. Other methods should gradually simplify the signature. > 2) Provide a symmetrical callback method set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4030) Streamline PlatformTarget interface
[ https://issues.apache.org/jira/browse/IGNITE-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571915#comment-15571915 ] Pavel Tupitsyn edited comment on IGNITE-4030 at 10/13/16 2:43 PM: -- Further considerations: * Allocating a stream when it is not used is unacceptable. This is solved in inObjectStreamOutObjectStream. * Allocating a stream for a single primitive (bool, int, long, etc) is unacceptable. So InStreamOutLong should stay. Therefore: InStreamOutStream, InStreamOutObject, OutStream, OutObject can be merged to InObjectStreamOutObjectStream. Resulting method set: * InLongOutLong * InStreamOutLong * InObjectStreamOutObjectStream Should we add InLongOutStream for symmetry? Or InLongStreamOutLongStream instead of InStreamOutLong? was (Author: ptupitsyn): Further considerations: * Allocating a stream when it is not used is unacceptable. This is solved in inObjectStreamOutObjectStream. * Allocating a stream for a single primitive (bool, int, long, etc) is unacceptable. So InStreamOutLong should stay. > Streamline PlatformTarget interface > --- > > Key: IGNITE-4030 > URL: https://issues.apache.org/jira/browse/IGNITE-4030 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > 1) Review the set of inOut methods. There should be one uber-method which > takes a stream and an object, returns a stream and an object. This method > covers all use cases. Other methods should gradually simplify the signature. > 2) Provide a symmetrical callback method set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4011) Automatically compute hash codes for newly built binary objects
[
https://issues.apache.org/jira/browse/IGNITE-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572132#comment-15572132
]
Alexander Paschenko commented on IGNITE-4011:
-
After consulting few guys who are Committers, I have made few changes to the
API according to their notes.
First, the interface to hash and compare objects is now named
{{BinaryTypeIdentity}}, and it looks as follows:
{code:java}
/**
* Method to compute hash codes for new binary objects and compare them for
equality.
*/
public interface BinaryTypeIdentity {
/**
* @param obj Binary object builder.
* @return Hash code value.
*/
public int hash(BinaryObject obj);
/**
* Compare binary objects for equality in consistence with how hash code is
computed.
*
* @param o1 First object.
* @param o2 Second object.
* @return
*/
public boolean equals(BinaryObject o1, BinaryObject o2);
}
{code}
Second, {{BinaryTypeIdentity}} is now part not to {{CacheKeyConfiguration}},
but rather to {{BinaryTypeConfiguration}} - it makes sense as some objects may
be part of other objects, moreover, concepts of equality and hashing make sense
not only for keys.
Third, there are two default implementations a user could utilize - namely,
{{FullIdentity}} and {{FieldsListIdentity}}.
{{FullIdentity}} should be used when the objects compared definitely have the
same binary schema, and it hashes/compares objects based on their fields list
(sorted by id).
And {{FieldsListIdentity}} considers not all fields but only those listed by
user in configuration, in user specified order.
If the user has not specified identity in configuration, current mechanism
(explicit set hash code/byte array based one) will be used.
Configuration example:
{code:xml}
field1
field3
{code}
> Automatically compute hash codes for newly built binary objects
> ---
>
> Key: IGNITE-4011
> URL: https://issues.apache.org/jira/browse/IGNITE-4011
> Project: Ignite
> Issue Type: Task
> Components: binary, cache
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 1.8
>
>
> For binary keys built automatically inside SQL engine during INSERT or MERGE,
> we need to compute hash codes automatically because in this case the user
> does not interact with any builders and can't set hash code explicitly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-4011) Automatically compute hash codes for newly built binary objects
[
https://issues.apache.org/jira/browse/IGNITE-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572132#comment-15572132
]
Alexander Paschenko edited comment on IGNITE-4011 at 10/13/16 2:47 PM:
---
After consulting few guys who are Committers, I have made few changes to the
API according to their notes.
*First*, the interface to hash and compare objects is now named
{{BinaryTypeIdentity}}, and it looks as follows:
{code:java}
/**
* Method to compute hash codes for new binary objects and compare them for
equality.
*/
public interface BinaryTypeIdentity {
/**
* @param obj Binary object builder.
* @return Hash code value.
*/
public int hash(BinaryObject obj);
/**
* Compare binary objects for equality in consistence with how hash code is
computed.
*
* @param o1 First object.
* @param o2 Second object.
* @return
*/
public boolean equals(BinaryObject o1, BinaryObject o2);
}
{code}
*Second*, {{BinaryTypeIdentity}} is now part not to {{CacheKeyConfiguration}},
but rather to {{BinaryTypeConfiguration}} - it makes sense as some objects may
be part of other objects, moreover, concepts of equality and hashing make sense
not only for keys.
*Third*, there are two default implementations a user could utilize if they
don't need any custom one - namely, {{FullIdentity}} and {{FieldsListIdentity}}.
{{FullIdentity}} should be used when the objects compared definitely have the
same binary schema, and it hashes/compares objects based on their fields list
(sorted by id).
And {{FieldsListIdentity}} considers not all fields but only those listed by
user in configuration, in user specified order.
If the user has not specified identity in configuration, current mechanism
(explicit set hash code/byte array based one) will be used.
Configuration example:
{code:xml}
field1
field3
{code}
was (Author: al.psc):
After consulting few guys who are Committers, I have made few changes to the
API according to their notes.
First, the interface to hash and compare objects is now named
{{BinaryTypeIdentity}}, and it looks as follows:
{code:java}
/**
* Method to compute hash codes for new binary objects and compare them for
equality.
*/
public interface BinaryTypeIdentity {
/**
* @param obj Binary object builder.
* @return Hash code value.
*/
public int hash(BinaryObject obj);
/**
* Compare binary objects for equality in consistence with how hash code is
computed.
*
* @param o1 First object.
* @param o2 Second object.
* @return
*/
public boolean equals(BinaryObject o1, BinaryObject o2);
}
{code}
Second, {{BinaryTypeIdentity}} is now part not to {{CacheKeyConfiguration}},
but rather to {{BinaryTypeConfiguration}} - it makes sense as some objects may
be part of other objects, moreover, concepts of equality and hashing make sense
not only for keys.
Third, there are two default implementations a user could utilize - namely,
{{FullIdentity}} and {{FieldsListIdentity}}.
{{FullIdentity}} should be used when the objects compared definitely have the
same binary schema, and it hashes/compares objects based on their fields list
(sorted by id).
And {{FieldsListIdentity}} considers not all fields but only those listed by
user in configuration, in user specified order.
If the user has not specified identity in configuration, current mechanism
(explicit set hash code/byte array based one) will be used.
Configuration example:
{code:xml}
[jira] [Commented] (IGNITE-4030) Streamline PlatformTarget interface
[ https://issues.apache.org/jira/browse/IGNITE-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572187#comment-15572187 ] Pavel Tupitsyn commented on IGNITE-4030: Finally decided to keep most of the methods. Changes are: * Merge OutLong with InLongOutLong * Merge InObjectStreamOutStream with InObjectStreamOutObjectStream > Streamline PlatformTarget interface > --- > > Key: IGNITE-4030 > URL: https://issues.apache.org/jira/browse/IGNITE-4030 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > 1) Review the set of inOut methods. There should be one uber-method which > takes a stream and an object, returns a stream and an object. This method > covers all use cases. Other methods should gradually simplify the signature. > 2) Provide a symmetrical callback method set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-3133) Unable to get a reference to a cache inside TX on a node that is filtered out by a node filter
[
https://issues.apache.org/jira/browse/IGNITE-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Govorukhin resolved IGNITE-3133.
Resolution: Fixed
> Unable to get a reference to a cache inside TX on a node that is filtered out
> by a node filter
> --
>
> Key: IGNITE-3133
> URL: https://issues.apache.org/jira/browse/IGNITE-3133
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Dmitriy Govorukhin
> Fix For: 1.8
>
> Attachments: CacheNodeFilter.java, CacheNodeFilterExample.java
>
>
> It's impossible to get a reference to a cache (Ignite.cache("name")) inside
> of a transaction on a node that is filtered out with
> CacheConfiguration.nodeFilter (doesn't hold cache data). The following
> exception happens.
> {noformat}
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:527)
> ... 32 more
> Caused by: java.io.InvalidObjectException: Failed to find cache for name:
> red_cache
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.readResolve(GridCacheContext.java:2051)
> ... 37 more
> Caused by: java.lang.IllegalStateException: Failed to find cache for name:
> red_cache
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.readResolve(GridCacheContext.java:2046)
> ... 37 more
> {noformat}
> To reproduce:
> - start ExampleNodeStartup
> - start attached CacheNodeFilterExample
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3133) Unable to get a reference to a cache inside TX on a node that is filtered out by a node filter
[
https://issues.apache.org/jira/browse/IGNITE-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572213#comment-15572213
]
Dmitriy Govorukhin commented on IGNITE-3133:
It is not issue, it expected behavior, because first call to cache cannot be in
transaction.
> Unable to get a reference to a cache inside TX on a node that is filtered out
> by a node filter
> --
>
> Key: IGNITE-3133
> URL: https://issues.apache.org/jira/browse/IGNITE-3133
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Dmitriy Govorukhin
> Fix For: 1.8
>
> Attachments: CacheNodeFilter.java, CacheNodeFilterExample.java
>
>
> It's impossible to get a reference to a cache (Ignite.cache("name")) inside
> of a transaction on a node that is filtered out with
> CacheConfiguration.nodeFilter (doesn't hold cache data). The following
> exception happens.
> {noformat}
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:527)
> ... 32 more
> Caused by: java.io.InvalidObjectException: Failed to find cache for name:
> red_cache
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.readResolve(GridCacheContext.java:2051)
> ... 37 more
> Caused by: java.lang.IllegalStateException: Failed to find cache for name:
> red_cache
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.readResolve(GridCacheContext.java:2046)
> ... 37 more
> {noformat}
> To reproduce:
> - start ExampleNodeStartup
> - start attached CacheNodeFilterExample
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3133) Unable to get a reference to a cache inside TX on a node that is filtered out by a node filter
[
https://issues.apache.org/jira/browse/IGNITE-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572235#comment-15572235
]
Dmitriy Govorukhin commented on IGNITE-3133:
Issue in code, because if use cache in clouse compute, cache will serialize
too. See try { } scope.
{code:title=CacheNodeFilterExample.java|borderStyle=solid}
ignite.compute().broadcast(new IgniteRunnable() {
@IgniteInstanceResource
Ignite ignite;
@Override public void run() {
IgniteTransactions txs = ignite.transactions();
try (Transaction tx = txs.txStart()) {
IgniteCache cache =
ignite.cache(RED_ONLY_CACHE);
cache.put(1, 2);
}
// Size must be 0 on the nodes where the cache is not
deployed.
System.out.println("Red cache local size: " +
cache.localSize());
}
});;
{code}
Correct code.
{code:title=CacheNodeFilterExample.java|borderStyle=solid}
ignite.compute().broadcast(new IgniteRunnable() {
@IgniteInstanceResource
Ignite ignite;
@Override public void run() {
IgniteTransactions txs = ignite.transactions();
try (Transaction tx = txs.txStart()) {
IgniteCache cache =
ignite.cache(RED_ONLY_CACHE);
cache.put(1, 2);
System.out.println("Red cache local size: " +
cache.localSize());
}
}
});;
{code}
> Unable to get a reference to a cache inside TX on a node that is filtered out
> by a node filter
> --
>
> Key: IGNITE-3133
> URL: https://issues.apache.org/jira/browse/IGNITE-3133
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Denis Magda
>Assignee: Dmitriy Govorukhin
> Fix For: 1.8
>
> Attachments: CacheNodeFilter.java, CacheNodeFilterExample.java
>
>
> It's impossible to get a reference to a cache (Ignite.cache("name")) inside
> of a transaction on a node that is filtered out with
> CacheConfiguration.nodeFilter (doesn't hold cache data). The following
> exception happens.
> {noformat}
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.ignite.marshaller.optimized.OptimizedObjectInputStream.readExternalizable(OptimizedObjectInputStream.java:527)
> ... 32 more
> Caused by: java.io.InvalidObjectException: Failed to find cache for name:
> red_cache
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.readResolve(GridCacheContext.java:2051)
> ... 37 more
> Caused by: java.lang.IllegalStateException: Failed to find cache for name:
> red_cache
> at
> org.apache.ignite.internal.processors.cache.GridCacheContext.readResolve(GridCacheContext.java:2046)
> ... 37 more
> {noformat}
> To reproduce:
> - start ExampleNodeStartup
> - start attached CacheNodeFilterExample
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4074) Refactor future operations in PlatformTarget
Pavel Tupitsyn created IGNITE-4074: -- Summary: Refactor future operations in PlatformTarget Key: IGNITE-4074 URL: https://issues.apache.org/jira/browse/IGNITE-4074 Project: Ignite Issue Type: Sub-task Components: platforms Reporter: Pavel Tupitsyn Fix For: 1.8 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4030) Streamline PlatformTarget operation methods
[ https://issues.apache.org/jira/browse/IGNITE-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-4030: --- Summary: Streamline PlatformTarget operation methods (was: Streamline PlatformTarget interface) > Streamline PlatformTarget operation methods > --- > > Key: IGNITE-4030 > URL: https://issues.apache.org/jira/browse/IGNITE-4030 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > 1) Review the set of inOut methods. There should be one uber-method which > takes a stream and an object, returns a stream and an object. This method > covers all use cases. Other methods should gradually simplify the signature. > 2) Provide a symmetrical callback method set -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4074) Refactor future operations in PlatformTarget
[ https://issues.apache.org/jira/browse/IGNITE-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn reassigned IGNITE-4074: -- Assignee: Pavel Tupitsyn > Refactor future operations in PlatformTarget > > > Key: IGNITE-4074 > URL: https://issues.apache.org/jira/browse/IGNITE-4074 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4030) Streamline PlatformTarget operation methods
[ https://issues.apache.org/jira/browse/IGNITE-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-4030: --- Description: Review the set of inOut methods. There should be one uber-method which takes a stream and an object, returns a stream and an object. This method covers all use cases. Other methods should gradually simplify the signature. (was: 1) Review the set of inOut methods. There should be one uber-method which takes a stream and an object, returns a stream and an object. This method covers all use cases. Other methods should gradually simplify the signature. 2) Provide a symmetrical callback method set) > Streamline PlatformTarget operation methods > --- > > Key: IGNITE-4030 > URL: https://issues.apache.org/jira/browse/IGNITE-4030 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Review the set of inOut methods. There should be one uber-method which takes > a stream and an object, returns a stream and an object. This method covers > all use cases. Other methods should gradually simplify the signature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4074) Refactor future operations in PlatformTarget
[ https://issues.apache.org/jira/browse/IGNITE-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-4074: --- Description: Currently async operations are executed in two steps: - start an operation (Cache.Get) - get the future (UU.TargetListenFuture* methods) This separation is unnecessary. See if we can perform asyn operations in one JNI call. See how PlatformCache.OP_REBALANCE does this. > Refactor future operations in PlatformTarget > > > Key: IGNITE-4074 > URL: https://issues.apache.org/jira/browse/IGNITE-4074 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Currently async operations are executed in two steps: > - start an operation (Cache.Get) > - get the future (UU.TargetListenFuture* methods) > This separation is unnecessary. See if we can perform asyn operations in one > JNI call. See how PlatformCache.OP_REBALANCE does this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-4042) Refactor async operations
[ https://issues.apache.org/jira/browse/IGNITE-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn closed IGNITE-4042. -- > Refactor async operations > - > > Key: IGNITE-4042 > URL: https://issues.apache.org/jira/browse/IGNITE-4042 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Currently async operations are executed in two steps: > - start an operation (Cache.Get) > - get the future (UU.TargetListenFuture* methods) > This separation is unnecessary. See if we can perform asyn operations in one > JNI call. See how PlatformCache.OP_REBALANCE does this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4074) Refactor async (*future) operations in PlatformTarget
[ https://issues.apache.org/jira/browse/IGNITE-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn updated IGNITE-4074: --- Summary: Refactor async (*future) operations in PlatformTarget (was: Refactor future operations in PlatformTarget) > Refactor async (*future) operations in PlatformTarget > - > > Key: IGNITE-4074 > URL: https://issues.apache.org/jira/browse/IGNITE-4074 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Currently async operations are executed in two steps: > - start an operation (Cache.Get) > - get the future (UU.TargetListenFuture* methods) > This separation is unnecessary. See if we can perform asyn operations in one > JNI call. See how PlatformCache.OP_REBALANCE does this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4042) Refactor async operations
[ https://issues.apache.org/jira/browse/IGNITE-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-4042. Resolution: Duplicate > Refactor async operations > - > > Key: IGNITE-4042 > URL: https://issues.apache.org/jira/browse/IGNITE-4042 > Project: Ignite > Issue Type: Sub-task > Components: platforms >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 1.8 > > > Currently async operations are executed in two steps: > - start an operation (Cache.Get) > - get the future (UU.TargetListenFuture* methods) > This separation is unnecessary. See if we can perform asyn operations in one > JNI call. See how PlatformCache.OP_REBALANCE does this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4054) Add debug to trace HadoopMapReducePlanner results.
[ https://issues.apache.org/jira/browse/IGNITE-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15572423#comment-15572423 ] ASF GitHub Bot commented on IGNITE-4054: GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/1159 IGNITE-4054 Add debug to trace HadoopMapReducePlanner results You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4054 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1159.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 #1159 commit a4c63ae113931615e940ada2411ebce32dba5db8 Author: iveselovskiy Date: 2016-09-30T07:45:13Z IGNITE-3998: IGFS: Enabled IgfsAbstractSelfTest.testCreateConsistencyMultithreaded. This closes #1129. commit a12298c0baf19407f3110ba3c4f0aab88b67946d Author: Igor Sapego Date: 2016-09-30T08:00:51Z IGNITE-3868: ODBC: Fixed connection string parsing. This closes #1051. commit 5e7ef8644ad824b87d4797e59133eb783ff8b098 Author: vozerov-gridgain Date: 2016-10-03T07:37:25Z Merge branch 'ignite-1.6.9' into ignite-1.6.10 commit 59b46d3e6ea073d054ca2262d676b055a74bbb1f Author: vozerov-gridgain Date: 2016-10-03T07:40:04Z IGNITE-2881: Fixed SPI queries. commit 0b66d2d7b695cf370a4b8a717844ad67742c6090 Author: sboikov Date: 2016-10-03T09:04:03Z ignite-3601 Do not check version on commit for read-only serializable transactions. commit 9f211e413332931f0fb1190744ddd7c7f38fd213 Author: tledkov-gridgain Date: 2016-10-03T09:26:12Z IGNITE-3645: IGFS: Local secondary: Implemented update() operation. This closes #1003. commit fa698d6fcfde0006423ef009337dbef58ac62515 Author: vozerov-gridgain Date: 2016-10-03T10:33:12Z Fixed TcpDiscoverySnapshotHistoryTest intermittent failures caused by multicast IP finder. commit bba019fd5076412ca43c10a32fd300b6031ccd0b Author: vozerov-gridgain Date: 2016-10-03T14:25:20Z IGNITE-3980: Processed failing tests in query suites. This closes #1137. commit a92f20b5cc75e6b80b2731da0192723526b0c1dc Author: vozerov-gridgain Date: 2016-10-04T11:10:26Z IGNITE-3597: Removed static work directory. commit 23461b8d33922772ef8e7217e9e87b3f3b0b37b1 Author: vozerov-gridgain Date: 2016-10-06T07:14:59Z IGNITE-4001: Timeouts for threads in Ignite pools. This closes #1130. commit b94b0aeae4c42b1d35128c6b1de97e3fa318d497 Author: tledkov-gridgain Date: 2016-10-06T07:22:50Z IGNITE-3163 IGFS: Added working directory support to IgniteHadoopIgfsSecondaryFileSystem. This closes #1030. This closes #1058. This closes #1132. commit e6317e01fa8a0de03e15dcdd84a575c6b06ce701 Author: vozerov-gridgain Date: 2016-10-06T09:03:48Z IGNITE-3593 .NET: IgniteConfiguration.WorkDirectory has no effect. This closes #903. This closes #1145. commit 952be8b995050b34379006dd6e739da3fe3b49e3 Author: Dmitriy Govorukhin Date: 2016-10-07T12:00:09Z Squashed commit of the following: commit 566881b695b8bc00e618fe9a9b4c86a8fd563cc1 Author: sboikov Date: Fri Oct 7 13:08:38 2016 +0300 minor commit 7fe88a1cb21f794ee55a176ab36d895cbf916528 Author: Dmitriy Govorukhin Date: Thu Oct 6 11:11:24 2016 +0300 ignite-update-notifier fix after review (cherry picked from commit a10d2ff) commit f2de749f958a3b18dc479f8a5517d7bf9362b933 Author: Dmitriy Govorukhin Date: Tue Oct 4 12:12:08 2016 +0300 ignite-2079-2 optimize import and change url path (cherry picked from commit 830a3cf) commit 0d1be85ad55b0aa91224690d6c112ae92e8bc0a9 Author: Dmitriy Govorukhin Date: Thu Sep 29 19:54:54 2016 +0300 update-notifier remove parse xml, now parse like properties (cherry picked from commit 9ecaa29) commit e43bca6fb4528a7fc0dcb804a74fca1c59d7468b Author: Dmitriy Govorukhin Date: Tue Sep 27 17:07:21 2016 +0300 remove dom parser (cherry picked from commit d1653b2) commit b9c776a8423471706ecb1dc6176b38f23e799077 Author: Anton Vinogradov Date: 2016-10-10T08:52:57Z IGNITE-3235 Failed to initialize primitive boolean cache property of superclass commit f9a0676fad7fd6c23e3c91c10d7e0412ccb27c06 Author: vozerov-gridgain Date: 2016-10-11T07:23:01Z IGNITE-4041: Created separate processor for thread pools and refactored IO manager. This closes #1150. commit 9a6cfce659df40b0a4624f19fd91c217b74bafea Author: nikolay_tikhonov Date: 2016-10-11T10:59:57Z IGNITE-4014 Fixed "Transaction hangs if entry processor failed during serialization". This closes #1148. commit 1938a17b01fac1e08c30011180bbcc3ed7374d83 Autho
[jira] [Reopened] (IGNITE-4073) OFFHEAP cache context method isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov reopened IGNITE-4073: -- > OFFHEAP cache context method isOffHeapEnabled return false > -- > > Key: IGNITE-4073 > URL: https://issues.apache.org/jira/browse/IGNITE-4073 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > > Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return > false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. > I't seems to be a bug, because, really, entries are put to off-heap. > Due to this bug, TtlManager could not correctly evict expired entries that > can results in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-4073) OFFHEAP cache context method isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov resolved IGNITE-4073. -- Resolution: Not A Bug > OFFHEAP cache context method isOffHeapEnabled return false > -- > > Key: IGNITE-4073 > URL: https://issues.apache.org/jira/browse/IGNITE-4073 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Critical > > Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return > false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. > I't seems to be a bug, because, really, entries are put to off-heap. > Due to this bug, TtlManager could not correctly evict expired entries that > can results in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4073) OFFHEAP cache context method isOffHeapEnabled return false
[ https://issues.apache.org/jira/browse/IGNITE-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mashenkov updated IGNITE-4073: - Assignee: (was: Andrew Mashenkov) > OFFHEAP cache context method isOffHeapEnabled return false > -- > > Key: IGNITE-4073 > URL: https://issues.apache.org/jira/browse/IGNITE-4073 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Andrew Mashenkov >Priority: Critical > > Cache context method isOffHeapEnabled() and isSwapOrOffheapEnabled() return > false for OFFHEAP_TIRED memory model, but useOffheapEntry() returns true. > I't seems to be a bug, because, really, entries are put to off-heap. > Due to this bug, TtlManager could not correctly evict expired entries that > can results in OOME. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4075) Cassandra store should load all available data when no parameters are provided in loadCache()
Valentin Kulichenko created IGNITE-4075: --- Summary: Cassandra store should load all available data when no parameters are provided in loadCache() Key: IGNITE-4075 URL: https://issues.apache.org/jira/browse/IGNITE-4075 Project: Ignite Issue Type: Improvement Components: cache Affects Versions: 1.7 Reporter: Valentin Kulichenko Currently, the Cassandra store loads nothing if no explicit query is provided. This is very counterintuitive and confusing. Other store implementation load all the available data in this case, and I think we should fix it consistently for Cassandra store. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-4048) Web console: result panel is not displayed in case if first query is incorrect
[ https://issues.apache.org/jira/browse/IGNITE-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-4048. -- Assignee: (was: Pavel Konstantinov) > Web console: result panel is not displayed in case if first query is incorrect > -- > > Key: IGNITE-4048 > URL: https://issues.apache.org/jira/browse/IGNITE-4048 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov > > Create a new Query > Write 'select * from qwerty' > Execute > Observed: there is no result panel with error message below the query area. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-4048) Web console: result panel is not displayed in case if first query is incorrect
[ https://issues.apache.org/jira/browse/IGNITE-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574065#comment-15574065 ] Pavel Konstantinov commented on IGNITE-4048: Successfully tested. > Web console: result panel is not displayed in case if first query is incorrect > -- > > Key: IGNITE-4048 > URL: https://issues.apache.org/jira/browse/IGNITE-4048 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Pavel Konstantinov > > Create a new Query > Write 'select * from qwerty' > Execute > Observed: there is no result panel with error message below the query area. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4076) Web console: can not choose a cache by clicking on it
Pavel Konstantinov created IGNITE-4076: -- Summary: Web console: can not choose a cache by clicking on it Key: IGNITE-4076 URL: https://issues.apache.org/jira/browse/IGNITE-4076 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Priority: Minor # Open SQL page # Create a second query # Click by cache name In my case the page is scrolled up instead of cache selecting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1072) Need to automatically support LocalDateTime class in indexing
[
https://issues.apache.org/jira/browse/IGNITE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1072:
Fix Version/s: 1.8
> Need to automatically support LocalDateTime class in indexing
> -
>
> Key: IGNITE-1072
> URL: https://issues.apache.org/jira/browse/IGNITE-1072
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Priority: Critical
> Labels: Usability
> Fix For: 1.8
>
>
> Currently this query doesn't work if {{localDate}} is an instance of
> {{LocalDateTime}}:
> {code}
> SqlFieldsQuery qry = new SqlFieldsQuery(
> "SELECT localDate from MyObject " +
> "WHERE localDate = '2013-09-12T11:00'");
> {code}
> It's not supported because {{LocalDateTime}} is JDK8 class. But probably we
> can use reflection to solve this.
> Also need to go through all classes in {{java.time}} package and see if any
> of them need to be supported as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1072) Need to automatically support LocalDateTime class in indexing
[
https://issues.apache.org/jira/browse/IGNITE-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Valentin Kulichenko updated IGNITE-1072:
Priority: Critical (was: Major)
> Need to automatically support LocalDateTime class in indexing
> -
>
> Key: IGNITE-1072
> URL: https://issues.apache.org/jira/browse/IGNITE-1072
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Priority: Critical
> Labels: Usability
> Fix For: 1.8
>
>
> Currently this query doesn't work if {{localDate}} is an instance of
> {{LocalDateTime}}:
> {code}
> SqlFieldsQuery qry = new SqlFieldsQuery(
> "SELECT localDate from MyObject " +
> "WHERE localDate = '2013-09-12T11:00'");
> {code}
> It's not supported because {{LocalDateTime}} is JDK8 class. But probably we
> can use reflection to solve this.
> Also need to go through all classes in {{java.time}} package and see if any
> of them need to be supported as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-4077) Web console: 'export all' needs to be improved
Pavel Konstantinov created IGNITE-4077: -- Summary: Web console: 'export all' needs to be improved Key: IGNITE-4077 URL: https://issues.apache.org/jira/browse/IGNITE-4077 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Priority: Minor Currently opening the system dialog to save a file takes a very long time and during this time user thinks that 'export all' doesn't work. I suggest to show some kind of dialog to show fetching progress. And during this time all UI elements of this query should not be available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4077) Web console: 'export all' needs to be improved
[ https://issues.apache.org/jira/browse/IGNITE-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-4077: --- Description: Currently opening the system dialog to save a file takes a very long time and during this time user thinks that 'export all' doesn't work. I suggest to show some kind of dialog to show fetching progress. And during this time all UI elements of this query should not be available except a new one 'Cancel Export All'. was: Currently opening the system dialog to save a file takes a very long time and during this time user thinks that 'export all' doesn't work. I suggest to show some kind of dialog to show fetching progress. And during this time all UI elements of this query should not be available. > Web console: 'export all' needs to be improved > -- > > Key: IGNITE-4077 > URL: https://issues.apache.org/jira/browse/IGNITE-4077 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > > Currently opening the system dialog to save a file takes a very long time and > during this time user thinks that 'export all' doesn't work. > I suggest to show some kind of dialog to show fetching progress. And during > this time all UI elements of this query should not be available except a new > one 'Cancel Export All'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3731) Web Console: Add fetch first page only for query on SQL screen
[ https://issues.apache.org/jira/browse/IGNITE-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574116#comment-15574116 ] Pavel Konstantinov commented on IGNITE-3731: Tested fetching first page. > Web Console: Add fetch first page only for query on SQL screen > -- > > Key: IGNITE-3731 > URL: https://issues.apache.org/jira/browse/IGNITE-3731 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4078) Web console: pie chart is not refreshed in coner case
[ https://issues.apache.org/jira/browse/IGNITE-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-4078: --- Attachment: IGNITE-4078.png > Web console: pie chart is not refreshed in coner case > - > > Key: IGNITE-4078 > URL: https://issues.apache.org/jira/browse/IGNITE-4078 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > Attachments: IGNITE-4078.png > > > # execute SCAN > # open pie chart - you should see 'scan is not supported' > # write a valid query and Execute > Observed - no pie chart was painted, only legend is visible (see attachment) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4078) Web console: pie chart is not refreshed in coner case
Pavel Konstantinov created IGNITE-4078: -- Summary: Web console: pie chart is not refreshed in coner case Key: IGNITE-4078 URL: https://issues.apache.org/jira/browse/IGNITE-4078 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Priority: Minor Attachments: IGNITE-4078.png # execute SCAN # open pie chart - you should see 'scan is not supported' # write a valid query and Execute Observed - no pie chart was painted, only legend is visible (see attachment) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-3731) Web Console: Add fetch first page only for query on SQL screen
[ https://issues.apache.org/jira/browse/IGNITE-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov closed IGNITE-3731. -- Assignee: (was: Pavel Konstantinov) > Web Console: Add fetch first page only for query on SQL screen > -- > > Key: IGNITE-3731 > URL: https://issues.apache.org/jira/browse/IGNITE-3731 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Affects Versions: 1.8 >Reporter: Andrey Novikov >Priority: Minor > Fix For: 1.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4078) Web console: pie chart is not refreshed in corner case
[ https://issues.apache.org/jira/browse/IGNITE-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-4078: --- Summary: Web console: pie chart is not refreshed in corner case (was: Web console: pie chart is not refreshed in coner case) > Web console: pie chart is not refreshed in corner case > -- > > Key: IGNITE-4078 > URL: https://issues.apache.org/jira/browse/IGNITE-4078 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Priority: Minor > Attachments: IGNITE-4078.png > > > # execute SCAN > # open pie chart - you should see 'scan is not supported' > # write a valid query and Execute > Observed - no pie chart was painted, only legend is visible (see attachment) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4076) Web console: can not choose a cache by clicking on it
[ https://issues.apache.org/jira/browse/IGNITE-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-4076: --- Priority: Major (was: Minor) > Web console: can not choose a cache by clicking on it > - > > Key: IGNITE-4076 > URL: https://issues.apache.org/jira/browse/IGNITE-4076 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov > > # Open SQL page > # Create a second query > # Click by cache name > In my case the page is scrolled up instead of cache selecting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4079) Web console-SQL: cache name is not displayed for default cache (cache name is null) in 'show query' dialog
Pavel Konstantinov created IGNITE-4079: -- Summary: Web console-SQL: cache name is not displayed for default cache (cache name is null) in 'show query' dialog Key: IGNITE-4079 URL: https://issues.apache.org/jira/browse/IGNITE-4079 Project: Ignite Issue Type: Bug Components: wizards Reporter: Pavel Konstantinov Priority: Minor We should display ''. # choose cache # SCAN # click on 'show query' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-4080) Web console: Not work revert of node filter section on cache page
Vasiliy Sisko created IGNITE-4080: - Summary: Web console: Not work revert of node filter section on cache page Key: IGNITE-4080 URL: https://issues.apache.org/jira/browse/IGNITE-4080 Project: Ignite Issue Type: Bug Components: wizards Affects Versions: 1.8 Reporter: Vasiliy Sisko Assignee: Dmitriy Shabalin Fix For: 1.8 On caches page in Node filter section not work section undo button -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4080) Web console: Not work revert of node filter section on cache page
[ https://issues.apache.org/jira/browse/IGNITE-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasiliy Sisko updated IGNITE-4080: -- Description: On caches page in Node filter section not work section undo button angular.js:13920 TypeError: field.$setViewValue is not a function at revert.directive.js:36 at lodash.js:4833 at baseForOwn (lodash.js:2955) at Function.forOwn (lodash.js:12840) at Scope.exports.default.scope.revert (revert.directive.js:31) at fn (eval at compile (angular.js:14817), :4:313) at expensiveCheckFn (angular.js:15906) at callback (angular.js:25885) at Scope.$eval (angular.js:17682) at Scope.$apply (angular.js:17782) was:On caches page in Node filter section not work section undo button > Web console: Not work revert of node filter section on cache page > - > > Key: IGNITE-4080 > URL: https://issues.apache.org/jira/browse/IGNITE-4080 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.8 >Reporter: Vasiliy Sisko >Assignee: Dmitriy Shabalin > Fix For: 1.8 > > > On caches page in Node filter section not work section undo button > angular.js:13920 TypeError: field.$setViewValue is not a function > at revert.directive.js:36 > at lodash.js:4833 > at baseForOwn (lodash.js:2955) > at Function.forOwn (lodash.js:12840) > at Scope.exports.default.scope.revert (revert.directive.js:31) > at fn (eval at compile (angular.js:14817), :4:313) > at expensiveCheckFn (angular.js:15906) > at callback (angular.js:25885) > at Scope.$eval (angular.js:17682) > at Scope.$apply (angular.js:17782) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-4079) Web console-SQL: cache name is not displayed for default cache (cache name is null) in 'show query' dialog
[ https://issues.apache.org/jira/browse/IGNITE-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-4079: Assignee: Alexey Kuznetsov > Web console-SQL: cache name is not displayed for default cache (cache name is > null) in 'show query' dialog > -- > > Key: IGNITE-4079 > URL: https://issues.apache.org/jira/browse/IGNITE-4079 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > > We should display ''. > # choose cache > # SCAN > # click on 'show query' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4079) Web console-SQL: cache name is not displayed for default cache (cache name is null) in 'show query' dialog
[ https://issues.apache.org/jira/browse/IGNITE-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-4079: - Fix Version/s: 1.8 > Web console-SQL: cache name is not displayed for default cache (cache name is > null) in 'show query' dialog > -- > > Key: IGNITE-4079 > URL: https://issues.apache.org/jira/browse/IGNITE-4079 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.7 >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 1.8 > > > We should display ''. > # choose cache > # SCAN > # click on 'show query' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-4079) Web console-SQL: cache name is not displayed for default cache (cache name is null) in 'show query' dialog
[ https://issues.apache.org/jira/browse/IGNITE-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-4079: - Affects Version/s: 1.7 > Web console-SQL: cache name is not displayed for default cache (cache name is > null) in 'show query' dialog > -- > > Key: IGNITE-4079 > URL: https://issues.apache.org/jira/browse/IGNITE-4079 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 1.7 >Reporter: Pavel Konstantinov >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 1.8 > > > We should display ''. > # choose cache > # SCAN > # click on 'show query' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
