[jira] [Commented] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties
[
https://issues.apache.org/jira/browse/IGNITE-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794491#comment-16794491
]
ARAVINDA REDDY N commented on IGNITE-11508:
---
Hi [~ilyak]
Hope you are doing good.
I have completed the changed to allow yarn queue override feature for Yarn
deployment.
Change:
-> Introduced a new property IGNITE_YARN_QUEUE to override the queue using
cluster properties
-> if the property is not set by default we will use the "default" queue
Please review the patch attached and let me know your feedback and next steps.
Thanks,
Aravinda
> Yarn Ignite deployment: Add support to over ride queue name through cluster
> properties
> --
>
> Key: IGNITE-11508
> URL: https://issues.apache.org/jira/browse/IGNITE-11508
> Project: Ignite
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 2.7
>Reporter: ARAVINDA REDDY N
>Assignee: ARAVINDA REDDY N
>Priority: Minor
> Attachments:
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
>
> Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the
> cluster.properties. When i checked the IgniteYarnClient source code by
> default it is set to "default".
> // Finally, set-up ApplicationSubmissionContext for the application
> ApplicationSubmissionContext appContext =
> app.getApplicationSubmissionContext();
> appContext.setApplicationName("ignition"); // application name
> appContext.setAMContainerSpec(amContainer);
> appContext.setResource(capability);
> appContext.setQueue("default"); // queue
>
> It would be a great support if we can allow overriding it through cluster
> properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties
[
https://issues.apache.org/jira/browse/IGNITE-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARAVINDA REDDY N updated IGNITE-11508:
--
Attachment:
IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
> Yarn Ignite deployment: Add support to over ride queue name through cluster
> properties
> --
>
> Key: IGNITE-11508
> URL: https://issues.apache.org/jira/browse/IGNITE-11508
> Project: Ignite
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 2.7
>Reporter: ARAVINDA REDDY N
>Assignee: ARAVINDA REDDY N
>Priority: Minor
> Attachments:
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
>
> Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the
> cluster.properties. When i checked the IgniteYarnClient source code by
> default it is set to "default".
> // Finally, set-up ApplicationSubmissionContext for the application
> ApplicationSubmissionContext appContext =
> app.getApplicationSubmissionContext();
> appContext.setApplicationName("ignition"); // application name
> appContext.setAMContainerSpec(amContainer);
> appContext.setResource(capability);
> appContext.setQueue("default"); // queue
>
> It would be a great support if we can allow overriding it through cluster
> properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties
[
https://issues.apache.org/jira/browse/IGNITE-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARAVINDA REDDY N reassigned IGNITE-11508:
-
Assignee: Ilya Kasnacheev (was: ARAVINDA REDDY N)
Fix Version/s: 2.8
Attachment:
IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
I have completed the changed to allow yarn queue override feature for Yarn
deployment.
Change:
-> Introduced a new property IGNITE_YARN_QUEUE to override the queue in cluster
properties
-> if the property is not set by default we will use the "default" queue
-> Added a test case to test the override and default option
Please review the patch attached and let me know your feedback and next steps.
> Yarn Ignite deployment: Add support to over ride queue name through cluster
> properties
> --
>
> Key: IGNITE-11508
> URL: https://issues.apache.org/jira/browse/IGNITE-11508
> Project: Ignite
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 2.7
>Reporter: ARAVINDA REDDY N
>Assignee: Ilya Kasnacheev
>Priority: Minor
> Fix For: 2.8
>
> Attachments:
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch,
>
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
>
> Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the
> cluster.properties. When i checked the IgniteYarnClient source code by
> default it is set to "default".
> // Finally, set-up ApplicationSubmissionContext for the application
> ApplicationSubmissionContext appContext =
> app.getApplicationSubmissionContext();
> appContext.setApplicationName("ignition"); // application name
> appContext.setAMContainerSpec(amContainer);
> appContext.setResource(capability);
> appContext.setQueue("default"); // queue
>
> It would be a great support if we can allow overriding it through cluster
> properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties
[
https://issues.apache.org/jira/browse/IGNITE-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARAVINDA REDDY N updated IGNITE-11508:
--
Attachment: (was:
IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch)
> Yarn Ignite deployment: Add support to over ride queue name through cluster
> properties
> --
>
> Key: IGNITE-11508
> URL: https://issues.apache.org/jira/browse/IGNITE-11508
> Project: Ignite
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 2.7
>Reporter: ARAVINDA REDDY N
>Assignee: Ilya Kasnacheev
>Priority: Minor
> Fix For: 2.8
>
> Attachments:
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
>
> Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the
> cluster.properties. When i checked the IgniteYarnClient source code by
> default it is set to "default".
> // Finally, set-up ApplicationSubmissionContext for the application
> ApplicationSubmissionContext appContext =
> app.getApplicationSubmissionContext();
> appContext.setApplicationName("ignition"); // application name
> appContext.setAMContainerSpec(amContainer);
> appContext.setResource(capability);
> appContext.setQueue("default"); // queue
>
> It would be a great support if we can allow overriding it through cluster
> properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-11508) Yarn Ignite deployment: Add support to over ride queue name through cluster properties
[
https://issues.apache.org/jira/browse/IGNITE-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ARAVINDA REDDY N updated IGNITE-11508:
--
Comment: was deleted
(was: Hi [~ilyak]
Hope you are doing good.
I have completed the changed to allow yarn queue override feature for Yarn
deployment.
Change:
-> Introduced a new property IGNITE_YARN_QUEUE to override the queue using
cluster properties
-> if the property is not set by default we will use the "default" queue
Please review the patch attached and let me know your feedback and next steps.
Thanks,
Aravinda
)
> Yarn Ignite deployment: Add support to over ride queue name through cluster
> properties
> --
>
> Key: IGNITE-11508
> URL: https://issues.apache.org/jira/browse/IGNITE-11508
> Project: Ignite
> Issue Type: Improvement
> Components: yarn
>Affects Versions: 2.7
>Reporter: ARAVINDA REDDY N
>Assignee: Ilya Kasnacheev
>Priority: Minor
> Fix For: 2.8
>
> Attachments:
> IGNITE_11508_Implemented_yarn_queue_override_feature_for_Yarn_Deployment.patch
>
>
> Yarn ignite 2.7.0 doesn't have the facility to provide queue name through the
> cluster.properties. When i checked the IgniteYarnClient source code by
> default it is set to "default".
> // Finally, set-up ApplicationSubmissionContext for the application
> ApplicationSubmissionContext appContext =
> app.getApplicationSubmissionContext();
> appContext.setApplicationName("ignition"); // application name
> appContext.setAMContainerSpec(amContainer);
> appContext.setResource(capability);
> appContext.setQueue("default"); // queue
>
> It would be a great support if we can allow overriding it through cluster
> properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11555) Unable to await partitions release latch caused by coordinator failover
[ https://issues.apache.org/jira/browse/IGNITE-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11555: -- Priority: Critical (was: Major) > Unable to await partitions release latch caused by coordinator failover > --- > > Key: IGNITE-11555 > URL: https://issues.apache.org/jira/browse/IGNITE-11555 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Priority: Critical > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11555) Unable to await partitions release latch caused by coordinator failover
[ https://issues.apache.org/jira/browse/IGNITE-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11555: -- Ignite Flags: (was: Docs Required) > Unable to await partitions release latch caused by coordinator failover > --- > > Key: IGNITE-11555 > URL: https://issues.apache.org/jira/browse/IGNITE-11555 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11555) Unable to await partitions release latch caused by coordinator failover
[ https://issues.apache.org/jira/browse/IGNITE-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11555: -- Fix Version/s: 2.8 > Unable to await partitions release latch caused by coordinator failover > --- > > Key: IGNITE-11555 > URL: https://issues.apache.org/jira/browse/IGNITE-11555 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Priority: Critical > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11555) Unable to await partitions release latch caused by coordinator failover
[ https://issues.apache.org/jira/browse/IGNITE-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk reassigned IGNITE-11555: - Assignee: Alexey Goncharuk > Unable to await partitions release latch caused by coordinator failover > --- > > Key: IGNITE-11555 > URL: https://issues.apache.org/jira/browse/IGNITE-11555 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Critical > Fix For: 2.8 > > > Currently exchanges latches (both server and client) are deleted when the > latch is completed. This leads to a hang in the following scenario: > 1) A grid with several nodes starts exchange latch sync > 2) All nodes send acks to coordinator > 3) Coordinator processes acks and sends final acks to some of the nodes > 4) These nodes process acks, complete and delete client latches > 5) Coordinator fails > 6) Nodes which did not receive final acks re-send the ack to a new coordinator > 7) Since the new coordinator already completed and deleted the client latch, > it does not process re-sent ack correctly and only adds it to the pending > messages. > Looks like the root cause of this issue is latch deletion on final ack. We > can safely delete the latch only when all nodes are guaranteed to process the > messages. Luckily, since the latch is tied to the exchange process, we can > safely delete the latch when the corresponding exchange completes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11555) Unable to await partitions release latch caused by coordinator failover
[ https://issues.apache.org/jira/browse/IGNITE-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11555: -- Description: Currently exchanges latches (both server and client) are deleted when the latch is completed. This leads to a hang in the following scenario: 1) A grid with several nodes starts exchange latch sync 2) All nodes send acks to coordinator 3) Coordinator processes acks and sends final acks to some of the nodes 4) These nodes process acks, complete and delete client latches 5) Coordinator fails 6) Nodes which did not receive final acks re-send the ack to a new coordinator 7) Since the new coordinator already completed and deleted the client latch, it does not process re-sent ack correctly and only adds it to the pending messages. Looks like the root cause of this issue is latch deletion on final ack. We can safely delete the latch only when all nodes are guaranteed to process the messages. Luckily, since the latch is tied to the exchange process, we can safely delete the latch when the corresponding exchange completes. > Unable to await partitions release latch caused by coordinator failover > --- > > Key: IGNITE-11555 > URL: https://issues.apache.org/jira/browse/IGNITE-11555 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Priority: Critical > Fix For: 2.8 > > > Currently exchanges latches (both server and client) are deleted when the > latch is completed. This leads to a hang in the following scenario: > 1) A grid with several nodes starts exchange latch sync > 2) All nodes send acks to coordinator > 3) Coordinator processes acks and sends final acks to some of the nodes > 4) These nodes process acks, complete and delete client latches > 5) Coordinator fails > 6) Nodes which did not receive final acks re-send the ack to a new coordinator > 7) Since the new coordinator already completed and deleted the client latch, > it does not process re-sent ack correctly and only adds it to the pending > messages. > Looks like the root cause of this issue is latch deletion on final ack. We > can safely delete the latch only when all nodes are guaranteed to process the > messages. Luckily, since the latch is tied to the exchange process, we can > safely delete the latch when the corresponding exchange completes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11555) Unable to await partitions release latch caused by coordinator failover
Alexey Goncharuk created IGNITE-11555: - Summary: Unable to await partitions release latch caused by coordinator failover Key: IGNITE-11555 URL: https://issues.apache.org/jira/browse/IGNITE-11555 Project: Ignite Issue Type: Bug Reporter: Alexey Goncharuk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5962) Increase max length of index name
[ https://issues.apache.org/jira/browse/IGNITE-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794578#comment-16794578 ] Pavel Kuznetsov commented on IGNITE-5962: - rerun : https://ci.ignite.apache.org/viewLog.html?buildId=3338711&; > Increase max length of index name > - > > Key: IGNITE-5962 > URL: https://issues.apache.org/jira/browse/IGNITE-5962 > Project: Ignite > Issue Type: Improvement > Components: general, sql >Affects Versions: 2.1 >Reporter: Ilya Lantukh >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length > was reduced from 768 to 256 bytes. If we need to support longer names, we > need to change format of metastore data pages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11226) SQL: Remove GridQueryIndexing.prepareNativeStatement
[ https://issues.apache.org/jira/browse/IGNITE-11226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794610#comment-16794610 ] Pavel Kuznetsov commented on IGNITE-11226: -- rerun : https://ci.ignite.apache.org/viewQueued.html?itemId=3339843&tab=queuedBuildOverviewTab > SQL: Remove GridQueryIndexing.prepareNativeStatement > > > Key: IGNITE-11226 > URL: https://issues.apache.org/jira/browse/IGNITE-11226 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Pavel Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > This method is the only leak of H2 internals to the outer code. Close > analysis of code reveals that the only reason we have it is *JDBC metadata*. > Need to create a method which will prepare metadata for a statement and > return it as a detached object. Most probably we already have all necessary > mechanics. This is more about refactoring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-7757) Unable to create a new cache via REST in special case
[
https://issues.apache.org/jira/browse/IGNITE-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794624#comment-16794624
]
Saikat Maitra edited comment on IGNITE-7757 at 3/18/19 12:32 AM:
-
[~pkonstantinov]
I was trying to reproduce the issue in local and when I tried the second
request
{code:java}
http://localhost:8080/ignite?cmd=getorcreate&cacheName=cache1
{code}
I was able to get successful response as below
{code:java}
{
successStatus: 0, error: null, sessionToken: null, response: null
}
{code}
Regards,
Saikat
was (Author: samaitra):
[~pkonstantinov]
I was trying to reproduce the issue in local and when I tried the second
request
{code:java}
http://localhost:8080/ignite?cmd=getorcreate&cacheName=cache1
{code}
I was able to get successful response as below
{{}}
{code:java}
{
successStatus: 0, error: null, sessionToken: null, response: null
}
{code}
Regards,
Saikat
> Unable to create a new cache via REST in special case
> -
>
> Key: IGNITE-7757
> URL: https://issues.apache.org/jira/browse/IGNITE-7757
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Major
>
> 1. try to start a new cache with non-existing data region
> {code}
> localhost:8080/ignite?cmd=getorcreate&cacheName=cache1&dataRegion=
> {code}
> You will get correct error message
> {code}
> "Failed to handle request: [req=GET_OR_CREATE_CACHE, err=Requested DataRegion
> is not configured: ]"
> {code}
> 2. then edit your request and make it correct and try again
> {code}
> localhost:8080/ignite?cmd=getorcreate&cacheName=cache1
> {code}
> You will get the same error message
> {code}
> "Failed to handle request: [req=GET_OR_CREATE_CACHE, err=Requested DataRegion
> is not configured: ]"
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7757) Unable to create a new cache via REST in special case
[
https://issues.apache.org/jira/browse/IGNITE-7757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794624#comment-16794624
]
Saikat Maitra commented on IGNITE-7757:
---
[~pkonstantinov]
I was trying to reproduce the issue in local and when I tried the second
request
{code:java}
http://localhost:8080/ignite?cmd=getorcreate&cacheName=cache1
{code}
I was able to get successful response as below
{{}}
{code:java}
{
successStatus: 0, error: null, sessionToken: null, response: null
}
{code}
Regards,
Saikat
> Unable to create a new cache via REST in special case
> -
>
> Key: IGNITE-7757
> URL: https://issues.apache.org/jira/browse/IGNITE-7757
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Priority: Major
>
> 1. try to start a new cache with non-existing data region
> {code}
> localhost:8080/ignite?cmd=getorcreate&cacheName=cache1&dataRegion=
> {code}
> You will get correct error message
> {code}
> "Failed to handle request: [req=GET_OR_CREATE_CACHE, err=Requested DataRegion
> is not configured: ]"
> {code}
> 2. then edit your request and make it correct and try again
> {code}
> localhost:8080/ignite?cmd=getorcreate&cacheName=cache1
> {code}
> You will get the same error message
> {code}
> "Failed to handle request: [req=GET_OR_CREATE_CACHE, err=Requested DataRegion
> is not configured: ]"
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11556) Add color legend into series selection panel
Alexander Kalinin created IGNITE-11556: -- Summary: Add color legend into series selection panel Key: IGNITE-11556 URL: https://issues.apache.org/jira/browse/IGNITE-11556 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Alexander Kalinin Currently we have a seris selector for charts, but it lacks color indication for matching series. Let's add them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11398) Remove leftover @RunWith(JUnit4.class)
[
https://issues.apache.org/jira/browse/IGNITE-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794750#comment-16794750
]
Ignite TC Bot commented on IGNITE-11398:
{panel:title=--> Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3336580&buildTypeId=IgniteTests24Java8_RunAll]
> Remove leftover @RunWith(JUnit4.class)
> --
>
> Key: IGNITE-11398
> URL: https://issues.apache.org/jira/browse/IGNITE-11398
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 20m
> Remaining Estimate: 0h
>
> During migration to junit4 transitional construction
> {{@RunWith(JUnit4.class)}} was used. And it was forgotten in couple of
> places. Let's clean up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11356) Test framework: Remove custom assumption exceptions handling
[
https://issues.apache.org/jira/browse/IGNITE-11356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794751#comment-16794751
]
Ignite TC Bot commented on IGNITE-11356:
{panel:title=--> Run :: All (Nightly): No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All (Nightly)*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3336716&buildTypeId=IgniteTests24Java8_RunAllNightly]
> Test framework: Remove custom assumption exceptions handling
>
>
> Key: IGNITE-11356
> URL: https://issues.apache.org/jira/browse/IGNITE-11356
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It turns out that custom handling of {{AssumptionViolatedException}} can be
> removed. Currently with custom handling tests with unmet assumptions are
> marked as passed. With default handling failed assumptions on instance level
> mark tests as ignored.
> Note: on class level reporting in case of unmet assumptions does not look
> perfect. But with custom handling a particular test is not included into TC
> report at all.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11556) Add color legend into series selection panel
[ https://issues.apache.org/jira/browse/IGNITE-11556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-11556: -- Description: Currently we have a series selector for charts, but it lacks color indication for matching series. Let's add them. (was: Currently we have a seris selector for charts, but it lacks color indication for matching series. Let's add them.) > Add color legend into series selection panel > > > Key: IGNITE-11556 > URL: https://issues.apache.org/jira/browse/IGNITE-11556 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently we have a series selector for charts, but it lacks color indication > for matching series. Let's add them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
