[jira] [Commented] (IGNITE-12192) visorcmd hangs if you ^D to quit
[ https://issues.apache.org/jira/browse/IGNITE-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939614#comment-16939614 ] Alexey Kuznetsov commented on IGNITE-12192: --- [~sdarlington] After looking around, I found this issue: "Customizable Ctrl-D handling #201" https://github.com/jline/jline2/issues/201 There 2 possible workarounds: 1. Handle EOFException (see org.apache.ignite.visor.visor#readLineOpt) 2. Update to jline3. Current version is jline 2.12.1 (may help without fixing code, but may be incompatible with VisorCmd current code) > visorcmd hangs if you ^D to quit > > > Key: IGNITE-12192 > URL: https://issues.apache.org/jira/browse/IGNITE-12192 > Project: Ignite > Issue Type: Bug > Components: visor >Affects Versions: 2.7.5 >Reporter: Stephen Darlington >Assignee: Stephen Darlington >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > You can exit most Unix utilities by pressing ^D. However, if you do that in > ignitevisorcmd when you're connected to a cluster, the process hangs. You > have to press ^C to quit. (It does work as expected if you close the > connection first.) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939612#comment-16939612 ] Nikolay Izhikov commented on IGNITE-12209: -- > must be added to output. columns except "cache ids/names" added. Please, take a look. > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939606#comment-16939606 ] Nikolay Izhikov commented on IGNITE-12209: -- [~ascherbakov] As of {{cache ids/names}}, I think we should export transaction keys as a separate system view because of performance. Building cache ids by iterating on transaction entries for each row seems inefficient. What do you think? > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12239) Transaction keys system view
Nikolay Izhikov created IGNITE-12239: Summary: Transaction keys system view Key: IGNITE-12239 URL: https://issues.apache.org/jira/browse/IGNITE-12239 Project: Ignite Issue Type: Sub-task Reporter: Nikolay Izhikov We should export transaction keys as a system view -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939578#comment-16939578 ] Nikolay Izhikov commented on IGNITE-12209: -- > Do you think it's possible to implement grid global system views in future ? I think technically it's possible. But I think we shouldn't do it. >From my point of view system views and metrics should stay local only. But, we should get a tracing framework that, I think, will be provided by [~agura], shortly. We will be able to trace all transactions and their mutual influence. > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939577#comment-16939577 ] Alexei Scherbakov commented on IGNITE-12209: [~nizhikov] This is sad. Such feature would allow to produce interesting views on transaction snapshots. I don't know implementation details but in theory it should work out of the box using current SQL engine and distributed joins. Do you think it's possible to implement grid global system views in future ? > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939571#comment-16939571 ] Nikolay Izhikov edited comment on IGNITE-12209 at 9/27/19 4:03 PM: --- Hello, [~ascherbakov] Thanks for the review. WIll add properties, shortly. > Would it be possible to construct whole distributed transaction using SQL > joins (joining by parent and local node) ? For now, We export only local data in metrics and system views. So, the answer is no, I think. was (Author: nizhikov): Hello, [~ascherbakov] Thanks for the review. WIll add properties, shortly. > Would it be possible to construct whole distributed transaction using SQL > joins (joining by parent and local node) ? For now, We export only local data in metrics and system view. So, the answer is no, I think. > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939571#comment-16939571 ] Nikolay Izhikov commented on IGNITE-12209: -- Hello, [~ascherbakov] Thanks for the review. WIll add properties, shortly. > Would it be possible to construct whole distributed transaction using SQL > joins (joining by parent and local node) ? For now, We export only local data in metrics and system view. So, the answer is no, I think. > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12209) Transaction system view
[ https://issues.apache.org/jira/browse/IGNITE-12209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939567#comment-16939567 ] Alexei Scherbakov commented on IGNITE-12209: [~nizhikov] I think * parent node id (tx.originatingNodeId), * near node id (tx.otherNodeId), * mapped topVer, * duration, * number of currently enlisted keys, * cache ids/names must be added to output. Note what tx.nodeId is not originating but local node for tx. You should change javadoc. Would it be possible to construct whole distributed transaction using SQL joins (joining by parent and local node) ? > Transaction system view > --- > > Key: IGNITE-12209 > URL: https://issues.apache.org/jira/browse/IGNITE-12209 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7.6 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add transactions to the system views. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12192) visorcmd hangs if you ^D to quit
[ https://issues.apache.org/jira/browse/IGNITE-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939551#comment-16939551 ] Stephen Darlington commented on IGNITE-12192: - [~kuaw26], it already _does_ support ^D. It only fails if you're connected to a cluster when you press it. Why should ^D only work sometimes? Also, visor is as much a Unix utility as, say, the Scala REPL or Python, both of which support ^D. My guess is they also support ^Z when run in Windows, which is the convention on that platform. > visorcmd hangs if you ^D to quit > > > Key: IGNITE-12192 > URL: https://issues.apache.org/jira/browse/IGNITE-12192 > Project: Ignite > Issue Type: Bug > Components: visor >Affects Versions: 2.7.5 >Reporter: Stephen Darlington >Assignee: Stephen Darlington >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > You can exit most Unix utilities by pressing ^D. However, if you do that in > ignitevisorcmd when you're connected to a cluster, the process hangs. You > have to press ^C to quit. (It does work as expected if you close the > connection first.) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12213) Sql objects system views
[ https://issues.apache.org/jira/browse/IGNITE-12213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939545#comment-16939545 ] Nikolay Izhikov commented on IGNITE-12213: -- I added the following system views in this ticket: # schemas # tables # views # indexes # table_columns # view_columns > Sql objects system views > > > Key: IGNITE-12213 > URL: https://issues.apache.org/jira/browse/IGNITE-12213 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE-12145 finished > We should add SQL objects system views. > * Schemas > * Tables > * Indexes > * SQL queries -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12192) visorcmd hangs if you ^D to quit
[ https://issues.apache.org/jira/browse/IGNITE-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939524#comment-16939524 ] Alexey Kuznetsov edited comment on IGNITE-12192 at 9/27/19 3:08 PM: [~sdarlington] Not sure that we should fix this. According to this: https://superuser.com/questions/169051/whats-the-difference-between-c-and-d-for-unix-mac-os-x-terminal Ctrl+C - means “interrupt”, i.e., stop what you're doing. Ctrl+D - means end of file. So, why we need to support Ctrl+D? VisorCmd is not a linux Utility - it is a 'sh' script that starts a program in JVM. So it looks for me that bash and|or JVM do not support "Ctrl+D". was (Author: kuaw26): [~sdarlington] Not sure that we should fix this. According to this: https://superuser.com/questions/169051/whats-the-difference-between-c-and-d-for-unix-mac-os-x-terminal Ctrl+C - means “interrupt”, i.e., stop what you're doing. Ctrl+D - means end of file. So, why we need to support Ctrl+D? VisorCmd is not a linux Utility - it is a 'sh' script that starts a program in JVM. > visorcmd hangs if you ^D to quit > > > Key: IGNITE-12192 > URL: https://issues.apache.org/jira/browse/IGNITE-12192 > Project: Ignite > Issue Type: Bug > Components: visor >Affects Versions: 2.7.5 >Reporter: Stephen Darlington >Assignee: Stephen Darlington >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > You can exit most Unix utilities by pressing ^D. However, if you do that in > ignitevisorcmd when you're connected to a cluster, the process hangs. You > have to press ^C to quit. (It does work as expected if you close the > connection first.) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12192) visorcmd hangs if you ^D to quit
[ https://issues.apache.org/jira/browse/IGNITE-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939524#comment-16939524 ] Alexey Kuznetsov commented on IGNITE-12192: --- [~sdarlington] Not sure that we should fix this. According to this: https://superuser.com/questions/169051/whats-the-difference-between-c-and-d-for-unix-mac-os-x-terminal Ctrl+C - means “interrupt”, i.e., stop what you're doing. Ctrl+D - means end of file. So, why we need to support Ctrl+D? VisorCmd is not a linux Utility - it is a 'sh' script that starts a program in JVM. > visorcmd hangs if you ^D to quit > > > Key: IGNITE-12192 > URL: https://issues.apache.org/jira/browse/IGNITE-12192 > Project: Ignite > Issue Type: Bug > Components: visor >Affects Versions: 2.7.5 >Reporter: Stephen Darlington >Assignee: Stephen Darlington >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > You can exit most Unix utilities by pressing ^D. However, if you do that in > ignitevisorcmd when you're connected to a cluster, the process hangs. You > have to press ^C to quit. (It does work as expected if you close the > connection first.) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-11132) Web console: scrolling to invalid field works incorrectly under the MS Edge
[ https://issues.apache.org/jira/browse/IGNITE-11132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-11132. --- Resolution: Won't Fix > Web console: scrolling to invalid field works incorrectly under the MS Edge > --- > > Key: IGNITE-11132 > URL: https://issues.apache.org/jira/browse/IGNITE-11132 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Major > > Cluster - Advanced - General(panel) - Attempts count > Enter the -1 value > Save > An invalid value will be placed behind the viewport -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-11132) Web console: scrolling to invalid field works incorrectly under the MS Edge
[ https://issues.apache.org/jira/browse/IGNITE-11132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-11132. - > Web console: scrolling to invalid field works incorrectly under the MS Edge > --- > > Key: IGNITE-11132 > URL: https://issues.apache.org/jira/browse/IGNITE-11132 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Major > > Cluster - Advanced - General(panel) - Attempts count > Enter the -1 value > Save > An invalid value will be placed behind the viewport -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-9143. -- Resolution: Cannot Reproduce > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Minor > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query (it is better to input string like "12345"). > !screenshot-1.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-9143) Web console: SQL buttons are disabled in case when it must be enabled
[ https://issues.apache.org/jira/browse/IGNITE-9143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-9143. > Web console: SQL buttons are disabled in case when it must be enabled > - > > Key: IGNITE-9143 > URL: https://issues.apache.org/jira/browse/IGNITE-9143 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Minor > Attachments: screenshot-1.png > > > Create a new notebook. > Start writing a new query (it is better to input string like "12345"). > !screenshot-1.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-9967) Web console: an error in browser console on opepning Readme.txt in Project Structure modal
[ https://issues.apache.org/jira/browse/IGNITE-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-9967. > Web console: an error in browser console on opepning Readme.txt in Project > Structure modal > -- > > Key: IGNITE-9967 > URL: https://issues.apache.org/jira/browse/IGNITE-9967 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Minor > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-9967) Web console: an error in browser console on opepning Readme.txt in Project Structure modal
[ https://issues.apache.org/jira/browse/IGNITE-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-9967. -- Resolution: Cannot Reproduce > Web console: an error in browser console on opepning Readme.txt in Project > Structure modal > -- > > Key: IGNITE-9967 > URL: https://issues.apache.org/jira/browse/IGNITE-9967 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Minor > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9967) Web console: an error in browser console on opepning Readme.txt in Project Structure modal
[ https://issues.apache.org/jira/browse/IGNITE-9967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9967: - Ignite Flags: (was: Docs Required) > Web console: an error in browser console on opepning Readme.txt in Project > Structure modal > -- > > Key: IGNITE-9967 > URL: https://issues.apache.org/jira/browse/IGNITE-9967 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Ilya Borisov >Priority: Minor > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-7011) Web console: add more tests
[ https://issues.apache.org/jira/browse/IGNITE-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-7011. > Web console: add more tests > --- > > Key: IGNITE-7011 > URL: https://issues.apache.org/jira/browse/IGNITE-7011 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > > Web console does not have enough test coverage, let's fix that. > Rough plan: > 1. Choose E2E testing framework. > 2. Investigate/implement mechanism for reproducible test environment (backend > DB, running web-agent and Ignite clusters). > 3. Write some reproducible tests. > 4. Setup CI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-8997) Web Console: Need to remove all the icons from all modal windows
[ https://issues.apache.org/jira/browse/IGNITE-8997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-8997. > Web Console: Need to remove all the icons from all modal windows > > > Key: IGNITE-8997 > URL: https://issues.apache.org/jira/browse/IGNITE-8997 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexander Kalinin >Priority: Major > Attachments: icon.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-8997) Web Console: Need to remove all the icons from all modal windows
[ https://issues.apache.org/jira/browse/IGNITE-8997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov resolved IGNITE-8997. -- Resolution: Won't Fix This issue will not bring any significant benefits to Web Console. > Web Console: Need to remove all the icons from all modal windows > > > Key: IGNITE-8997 > URL: https://issues.apache.org/jira/browse/IGNITE-8997 > Project: Ignite > Issue Type: Improvement > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexander Kalinin >Priority: Major > Attachments: icon.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-9032) Remove extra dependecy from web console frontend
[ https://issues.apache.org/jira/browse/IGNITE-9032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-9032. > Remove extra dependecy from web console frontend > > > Key: IGNITE-9032 > URL: https://issues.apache.org/jira/browse/IGNITE-9032 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Alexander Kalinin >Assignee: Ilya Borisov >Priority: Minor > Original Estimate: 2h > Remaining Estimate: 2h > > Currently links checking tool for frontend uses 'app-root-path' package, but > it can be imple,ented with native nodejs 'path' module. Extra module should > be deleted. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12238) RobinHoodBackwardShiftHashMap works incorrectly on big endian architectures
Andrey N. Gura created IGNITE-12238: --- Summary: RobinHoodBackwardShiftHashMap works incorrectly on big endian architectures Key: IGNITE-12238 URL: https://issues.apache.org/jira/browse/IGNITE-12238 Project: Ignite Issue Type: Bug Reporter: Andrey N. Gura Assignee: Andrey N. Gura Fix For: 2.8 {{RobinHoodBackwardShiftHashMap}} has bug that can be reproduced only on big endinan architectures. In order to reproduce the problem run the following tests: * {{RobinHoodBackwardShiftHashMapTest.testCollisionOnRemove}} * {{testRandomOpsPutRemove}} The problem is {{setIdealBucket()}} method writes {{long}} value to the offheap memory, while {{getIdealBucket()}} reads {{int}} value. For little endian architectures it works because meaningful 4 bytes will written first to the memory and leading zero bytes will be rewriteen by the next operation. On big endian architecture always 4 zero bytes will be written to the memory. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-11981) [IEP-35] Create MU shortcut instead of static import of MetricUtils
[ https://issues.apache.org/jira/browse/IGNITE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939461#comment-16939461 ] Andrey N. Gura edited comment on IGNITE-11981 at 9/27/19 1:40 PM: -- [~avinogradov], [~nizhikov] It seems that issue about some cosmetic which isn't issue yet. I think this ticket could be closed as "Won't fix". Do you agree? was (Author: agura): [~avinogradov], [~nizhikov] It seems that issue about some cosmetic which isn't issue yet. I think this ticket could be closed as "Won't fix". > [IEP-35] Create MU shortcut instead of static import of MetricUtils > --- > > Key: IGNITE-11981 > URL: https://issues.apache.org/jira/browse/IGNITE-11981 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Minor > Labels: IEP-35 > > More Ignite-way of coding is the usage of short cut classes. > We should use MU instead of static import of {{MetricUtils}}. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11981) [IEP-35] Create MU shortcut instead of static import of MetricUtils
[ https://issues.apache.org/jira/browse/IGNITE-11981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939461#comment-16939461 ] Andrey N. Gura commented on IGNITE-11981: - [~avinogradov], [~nizhikov] It seems that issue about some cosmetic which isn't issue yet. I think this ticket could be closed as "Won't fix". > [IEP-35] Create MU shortcut instead of static import of MetricUtils > --- > > Key: IGNITE-11981 > URL: https://issues.apache.org/jira/browse/IGNITE-11981 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Minor > Labels: IEP-35 > > More Ignite-way of coding is the usage of short cut classes. > We should use MU instead of static import of {{MetricUtils}}. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12197) Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
[ https://issues.apache.org/jira/browse/IGNITE-12197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939443#comment-16939443 ] Pavel Kovalenko commented on IGNITE-12197: -- [~agura] Looks good to me. Please proceed with merge. > Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl > -- > > Key: IGNITE-12197 > URL: https://issues.apache.org/jira/browse/IGNITE-12197 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey N. Gura >Assignee: Andrey N. Gura >Priority: Minor > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > IGNITE-12027 introduces possible bug due to incorrect way for getting value > of persistent enabled property in {{CacheGroupMetricsImpl}} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11094) Add SSL support for ignite zookeeper SPI
[ https://issues.apache.org/jira/browse/IGNITE-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939439#comment-16939439 ] Pavel Kovalenko commented on IGNITE-11094: -- [~SomeFire] Merged dependency fix for Kafka module > Add SSL support for ignite zookeeper SPI > > > Key: IGNITE-11094 > URL: https://issues.apache.org/jira/browse/IGNITE-11094 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Assignee: Ryabov Dmitrii >Priority: Major > Fix For: 2.8 > > Time Spent: 7h > Remaining Estimate: 0h > > ZK 3.5.4-beta is already supporting SSL [1]. We should add SSL support to ZK > server connections if Zookeeper SPI used. > 1. > https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-11375) Web console: Show appropriate message in no data component when demo is disabled on agent
[ https://issues.apache.org/jira/browse/IGNITE-11375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-11375: - Assignee: (was: Vasiliy Sisko) > Web console: Show appropriate message in no data component when demo is > disabled on agent > - > > Key: IGNITE-11375 > URL: https://issues.apache.org/jira/browse/IGNITE-11375 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Vasiliy Sisko >Priority: Major > Original Estimate: 2h > Time Spent: 1h > Remaining Estimate: 1h > > If the demo is opened and stay only an agent with disabled demo The no data > component should show appropriate message. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12237) Forbid thin client connections dynamically
Denis Mekhanikov created IGNITE-12237: - Summary: Forbid thin client connections dynamically Key: IGNITE-12237 URL: https://issues.apache.org/jira/browse/IGNITE-12237 Project: Ignite Issue Type: Improvement Components: thin client Reporter: Denis Mekhanikov Sometimes it's useful to forbid thin clients connections to nodes for some period of time. At this time cluster may be performing some activation needed for correct work of the application. It would be good to have an API call, opening and closing thin client connections. This feature was requested in the following StackOverflow question: https://stackoverflow.com/questions/58106297/how-to-block-java-thin-client-request-till-preloading-of-data-in-ignite-cluster -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-10626) Save authenticated Webconsole session for more than one page refresh
[ https://issues.apache.org/jira/browse/IGNITE-10626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-10626: - Assignee: (was: Vasiliy Sisko) > Save authenticated Webconsole session for more than one page refresh > > > Key: IGNITE-10626 > URL: https://issues.apache.org/jira/browse/IGNITE-10626 > Project: Ignite > Issue Type: Improvement >Reporter: Evgenii Zhuravlev >Priority: Major > > Now, it's needed to enter login and password after each page refresh -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12236) RepositoryFactorySupport#getQueryLookupStrategy no longer overriden in IgniteRepositoryFactory
[ https://issues.apache.org/jira/browse/IGNITE-12236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thibaut updated IGNITE-12236: - Affects Version/s: 2.8 > RepositoryFactorySupport#getQueryLookupStrategy no longer overriden in > IgniteRepositoryFactory > -- > > Key: IGNITE-12236 > URL: https://issues.apache.org/jira/browse/IGNITE-12236 > Project: Ignite > Issue Type: Bug > Components: spring >Affects Versions: 2.8, 2.7.6 >Reporter: Thibaut >Priority: Major > > Hello, > org.apache.ignite.springdata20.repository.support.IgniteRepositoryFactory#getQueryLookupStrategy > does not override > org.springframework.data.repository.core.support.RepositoryFactorySupport#getQueryLookupStrategy > since this commit > [https://github.com/spring-projects/spring-data-commons/commit/a6215fbe0f5c9a254cddacb12763737f2c286ad5] > > this results in a thrown exception in > org.springframework.data.repository.core.support.RepositoryFactorySupport.QueryExecutorMethodInterceptor#QueryExecutorMethodInterceptor > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12236) RepositoryFactorySupport#getQueryLookupStrategy no longer overriden in IgniteRepositoryFactory
Riquet Thibaut created IGNITE-12236: --- Summary: RepositoryFactorySupport#getQueryLookupStrategy no longer overriden in IgniteRepositoryFactory Key: IGNITE-12236 URL: https://issues.apache.org/jira/browse/IGNITE-12236 Project: Ignite Issue Type: Bug Components: spring Affects Versions: 2.7.6 Reporter: Riquet Thibaut Hello, org.apache.ignite.springdata20.repository.support.IgniteRepositoryFactory#getQueryLookupStrategy does not override org.springframework.data.repository.core.support.RepositoryFactorySupport#getQueryLookupStrategy since this commit [https://github.com/spring-projects/spring-data-commons/commit/a6215fbe0f5c9a254cddacb12763737f2c286ad5] this results in a thrown exception in org.springframework.data.repository.core.support.RepositoryFactorySupport.QueryExecutorMethodInterceptor#QueryExecutorMethodInterceptor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11992) Improvements for new security approach
[ https://issues.apache.org/jira/browse/IGNITE-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939366#comment-16939366 ] Ignite TC Bot commented on IGNITE-11992: {panel:title=Branch: [pull/6918/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *-- Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4639369buildTypeId=IgniteTests24Java8_RunAll] > Improvements for new security approach > -- > > Key: IGNITE-11992 > URL: https://issues.apache.org/jira/browse/IGNITE-11992 > Project: Ignite > Issue Type: Improvement > Components: security >Affects Versions: 2.8 >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1. The visor tasks lost permission. > The method VisorQueryUtils#scheduleQueryStart makes a new thread and loses > context. > 3. The GridRestProcessor does tasks outside "withContext" section. As result > context loses. > 4. The GridRestProcessor isn't client, we can't read security subject from > node attribute. > We should transmit secCtx for fake nodes and secSubjId for real. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12182) ExecutorService is inconsistent with Compute and Services, runs on clients
[ https://issues.apache.org/jira/browse/IGNITE-12182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939349#comment-16939349 ] Stephen Darlington commented on IGNITE-12182: - Would you mind taking a look, [~yzhdanov]? > ExecutorService is inconsistent with Compute and Services, runs on clients > -- > > Key: IGNITE-12182 > URL: https://issues.apache.org/jira/browse/IGNITE-12182 > Project: Ignite > Issue Type: Bug > Components: compute >Affects Versions: 2.7.5 >Reporter: Stephen Darlington >Assignee: Stephen Darlington >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > In IGNITE-860 the default behaviour was changed so that compute and service > tasks would be executed only on server nodes. This is a sensible default and > it's confusing that it's not also true for jobs run using the ExecutorService. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12192) visorcmd hangs if you ^D to quit
[ https://issues.apache.org/jira/browse/IGNITE-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939347#comment-16939347 ] Stephen Darlington commented on IGNITE-12192: - Would you mind taking a look, [~kuaw26] ? > visorcmd hangs if you ^D to quit > > > Key: IGNITE-12192 > URL: https://issues.apache.org/jira/browse/IGNITE-12192 > Project: Ignite > Issue Type: Bug > Components: visor >Affects Versions: 2.7.5 >Reporter: Stephen Darlington >Assignee: Stephen Darlington >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > You can exit most Unix utilities by pressing ^D. However, if you do that in > ignitevisorcmd when you're connected to a cluster, the process hangs. You > have to press ^C to quit. (It does work as expected if you close the > connection first.) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9836) Invalid check of ea java versions
[ https://issues.apache.org/jira/browse/IGNITE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939339#comment-16939339 ] Stephen Darlington commented on IGNITE-9836: Implemented review comments here: [https://github.com/apache/ignite/pull/6920] > Invalid check of ea java versions > - > > Key: IGNITE-9836 > URL: https://issues.apache.org/jira/browse/IGNITE-9836 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > On check of '1.8.0_192-ea' java version in ignite.sh the next messages in > console are printed: > {code:java} > ./include/functions.sh: line 81: [: -lt: unary operator expected > ./ignite.sh: line 61: > /home/vsisko/Downloads/distr/bin/include/build-classpath.sh: No such file or > directory > ./ignite.sh: line 152: [: -eq: unary operator expected > ./ignite.sh: line 157: [: -gt: unary operator expected > ./ignite.sh: line 170: [: -eq: unary operator expected{code} -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12189) Implement correct limit for TextQuery
[ https://issues.apache.org/jira/browse/IGNITE-12189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939338#comment-16939338 ] Yuriy Shuliha commented on IGNITE-12189: - [~yzhdanov] please review my pull-request in scope of ignite-core [~sergi] please review my pull-request in scope of ignite-indexing CC: [~dmagda] > Implement correct limit for TextQuery > - > > Key: IGNITE-12189 > URL: https://issues.apache.org/jira/browse/IGNITE-12189 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Yuriy Shuliha >Assignee: Yuriy Shuliha >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > PROBLEM > For now each server-node returns all response records to the client-node and > it may contain ~thousands, ~hundred thousands records. > Event if we need only first 10-100. Again, all the results are added to queue > in _*GridCacheQueryFutureAdapter*_ in arbitrary order by pages. > There are no any means to deliver deterministic result. > SOLUTION > Implement _*limit*_ as parameter for _*TextQuery*_ and > _*GridCacheQueryRequest*_ > It should be passed as limit parameter in Lucene's > _*IndexSearcher.search()*_ in _*GridLuceneIndex*_. > For distributed queries _*limit*_ will also trim response queue when merging > results. > Type: long > Special value: : 0 -> No limit (Long.MAX_VALUE); -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12189) Implement correct limit for TextQuery
[ https://issues.apache.org/jira/browse/IGNITE-12189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuriy Shuliha updated IGNITE-12189: Description: PROBLEM For now each server-node returns all response records to the client-node and it may contain ~thousands, ~hundred thousands records. Event if we need only first 10-100. Again, all the results are added to queue in _*GridCacheQueryFutureAdapter*_ in arbitrary order by pages. There are no any means to deliver deterministic result. SOLUTION Implement _*limit*_ as parameter for _*TextQuery*_ and _*GridCacheQueryRequest*_ It should be passed as limit parameter in Lucene's _*IndexSearcher.search()*_ in _*GridLuceneIndex*_. For distributed queries _*limit*_ will also trim response queue when merging results. Type: long Special value: : 0 -> No limit (Integer.MAX_VALUE); was: PROBLEM For now each server-node returns all response records to the client-node and it may contain ~thousands, ~hundred thousands records. Event if we need only first 10-100. Again, all the results are added to queue in _*GridCacheQueryFutureAdapter*_ in arbitrary order by pages. There are no any means to deliver deterministic result. SOLUTION Implement _*limit*_ as parameter for _*TextQuery*_ and _*GridCacheQueryRequest*_ It should be passed as limit parameter in Lucene's _*IndexSearcher.search()*_ in _*GridLuceneIndex*_. For distributed queries _*limit*_ will also trim response queue when merging results. Type: long Special value: : 0 -> No limit (Long.MAX_VALUE); > Implement correct limit for TextQuery > - > > Key: IGNITE-12189 > URL: https://issues.apache.org/jira/browse/IGNITE-12189 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Yuriy Shuliha >Assignee: Yuriy Shuliha >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > PROBLEM > For now each server-node returns all response records to the client-node and > it may contain ~thousands, ~hundred thousands records. > Event if we need only first 10-100. Again, all the results are added to > queue in _*GridCacheQueryFutureAdapter*_ in arbitrary order by pages. > There are no any means to deliver deterministic result. > SOLUTION > Implement _*limit*_ as parameter for _*TextQuery*_ and > _*GridCacheQueryRequest*_ > It should be passed as limit parameter in Lucene's > _*IndexSearcher.search()*_ in _*GridLuceneIndex*_. > For distributed queries _*limit*_ will also trim response queue when merging > results. > Type: long > Special value: : 0 -> No limit (Integer.MAX_VALUE); -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-6306) Visor CMD: Improvement of alert command
[ https://issues.apache.org/jira/browse/IGNITE-6306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-6306: Assignee: (was: Vasiliy Sisko) > Visor CMD: Improvement of alert command > --- > > Key: IGNITE-6306 > URL: https://issues.apache.org/jira/browse/IGNITE-6306 > Project: Ignite > Issue Type: Improvement > Components: wizards >Affects Versions: 2.1 >Reporter: Vasiliy Sisko >Priority: Major > > # Alerts by nodes should be separated for server and client nodes. > # Locate table with alerts first. > # Add to table of alerts unregistered alerts, show alert state, show > unregistered alert timestamp. > # Replace in all tables *send* word to *triggered*. > # In alerts table group *registered* / *unregistered* and *First triggered* / > *Last triggered* column pairs. Show data of that columns in 2 rows. > # In last triggered alerts table remove *registered* and *count* columns. > # Add argument to configure count of last triggered alerts. > # Remove showing of *(Not set)* from tables for alert without name. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-5867) Web console: Add parameter for adding primary key columns to generated POJO class
[ https://issues.apache.org/jira/browse/IGNITE-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-5867: Assignee: (was: Vasiliy Sisko) > Web console: Add parameter for adding primary key columns to generated POJO > class > - > > Key: IGNITE-5867 > URL: https://issues.apache.org/jira/browse/IGNITE-5867 > Project: Ignite > Issue Type: Improvement >Reporter: Evgenii Zhuravlev >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-3439) Caches: Add possibility to specify custom store and configure it via XML if needed.
[ https://issues.apache.org/jira/browse/IGNITE-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-3439: Assignee: (was: Vasiliy Sisko) > Caches: Add possibility to specify custom store and configure it via XML if > needed. > --- > > Key: IGNITE-3439 > URL: https://issues.apache.org/jira/browse/IGNITE-3439 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.6 >Reporter: Alexey Kuznetsov >Priority: Major > > For now we could select only builtin stores (pojo, hibernate,...) but no way > for user store. We should fix this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-2269) Implement additional constructors for Binary type configurations
[ https://issues.apache.org/jira/browse/IGNITE-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-2269: Assignee: (was: Vasiliy Sisko) > Implement additional constructors for Binary type configurations > > > Key: IGNITE-2269 > URL: https://issues.apache.org/jira/browse/IGNITE-2269 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.6 >Reporter: Vasiliy Sisko >Priority: Major > > Implement constructors with parameters and implement generation of java code > and xml config with that constructors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-1879) Add platforms configurations
[ https://issues.apache.org/jira/browse/IGNITE-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-1879: Assignee: (was: Vasiliy Sisko) > Add platforms configurations > > > Key: IGNITE-1879 > URL: https://issues.apache.org/jira/browse/IGNITE-1879 > Project: Ignite > Issue Type: Task > Components: wizards >Affects Versions: 1.5.0.final >Reporter: Alexey Kuznetsov >Priority: Major > > .NET C# configuration: IGNITE-1906 > .NET XML configuration: IGNITE-2380 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-1659) Add query history
[ https://issues.apache.org/jira/browse/IGNITE-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-1659: Assignee: (was: Vasiliy Sisko) > Add query history > - > > Key: IGNITE-1659 > URL: https://issues.apache.org/jira/browse/IGNITE-1659 > Project: Ignite > Issue Type: Task > Components: wizards >Reporter: Pavel Konstantinov >Priority: Major > > We need to implement saving query history and restoring query text into any > Query field. > Note: currently we have workaround - we save notebooks with all queries in > it, but if user remove notebook he lost all queries from this notebook. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12230) Partition eviction during cache stop / deactivation may cause errors leading to node failure and storage corruption
[ https://issues.apache.org/jira/browse/IGNITE-12230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939273#comment-16939273 ] Ignite TC Bot commented on IGNITE-12230: {panel:title=Branch: [pull/6906/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *-- Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=4633004buildTypeId=IgniteTests24Java8_RunAll] > Partition eviction during cache stop / deactivation may cause errors leading > to node failure and storage corruption > --- > > Key: IGNITE-12230 > URL: https://issues.apache.org/jira/browse/IGNITE-12230 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > PartitionEvictionTask may produce NullPointerException if cache / cache group > / cluser is stopping / deactivating. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11992) Improvements for new security approach
[ https://issues.apache.org/jira/browse/IGNITE-11992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16939211#comment-16939211 ] Stepachev Maksim commented on IGNITE-11992: --- New PR:https://github.com/apache/ignite/pull/6918 > Improvements for new security approach > -- > > Key: IGNITE-11992 > URL: https://issues.apache.org/jira/browse/IGNITE-11992 > Project: Ignite > Issue Type: Improvement > Components: security >Affects Versions: 2.8 >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1. The visor tasks lost permission. > The method VisorQueryUtils#scheduleQueryStart makes a new thread and loses > context. > 3. The GridRestProcessor does tasks outside "withContext" section. As result > context loses. > 4. The GridRestProcessor isn't client, we can't read security subject from > node attribute. > We should transmit secCtx for fake nodes and secSubjId for real. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12054) Upgrade Spark module to 2.4
[ https://issues.apache.org/jira/browse/IGNITE-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12054: - Affects Version/s: (was: 2.7.5) 2.8 > Upgrade Spark module to 2.4 > --- > > Key: IGNITE-12054 > URL: https://issues.apache.org/jira/browse/IGNITE-12054 > Project: Ignite > Issue Type: Task > Components: spark >Affects Versions: 2.8 >Reporter: Denis A. Magda >Assignee: Alexey Zinoviev >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Users can't use APIs that are already available in Spark 2.4: > https://stackoverflow.com/questions/57392143/persisting-spark-dataframe-to-ignite > Let's upgrade Spark from 2.3 to 2.4 until we extract the Spark Integration as > a separate module that can support multiple Spark versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)