[jira] [Comment Edited] (IGNITE-1614) Displaying of labels of x-axis is broken now
[ https://issues.apache.org/jira/browse/IGNITE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942922#comment-14942922 ] Pavel Konstantinov edited comment on IGNITE-1614 at 10/5/15 6:24 AM: - 1) Currently I'm observe that all labels are merged at the left side of the X-axis. They are unreadable. (ig-1614.png) 2) Line chart has no text labels on x-axis - only digits (see ig-1614-2.png), but should display 'Parking 1', 'Parking 2' and so on. was (Author: pkonstantinov): 1) Currently I'm observe that all labels are merged at the left side of the X-axis. They are unreadable. 2) Line chart has no text labels on x-axis - only digits (see ig-1614-2.png), but should display 'Parking 1', 'Parking 2' and so on. > Displaying of labels of x-axis is broken now > > > Key: IGNITE-1614 > URL: https://issues.apache.org/jira/browse/IGNITE-1614 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: ig-1614-2.png, ig-1614.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1614) Displaying of labels of x-axis is broken now
[ https://issues.apache.org/jira/browse/IGNITE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942922#comment-14942922 ] Pavel Konstantinov edited comment on IGNITE-1614 at 10/5/15 4:52 AM: - 1) Currently I'm observe that all labels are merged at the left side of the X-axis. They are unreadable. 2) Line chart has no text labels on x-axis - only digits (see ig-1614-2.png), but should display 'Parking 1', 'Parking 2' and so on. was (Author: pkonstantinov): 1) Currently I'm observe that all labels are merged at the left side of the X-axis. They are unreadable. 2) Line chart has no text labels on x-axis - only digits (see ig-1614-2.png) > Displaying of labels of x-axis is broken now > > > Key: IGNITE-1614 > URL: https://issues.apache.org/jira/browse/IGNITE-1614 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: ig-1614-2.png, ig-1614.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1614) Displaying of labels of x-axis is broken now
[ https://issues.apache.org/jira/browse/IGNITE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942922#comment-14942922 ] Pavel Konstantinov commented on IGNITE-1614: 1) Currently I'm observe that all labels are merged at the left side of the X-axis. They are unreadable. 2) Line chart has no text labels on x-axis - only digits (see ig-1614-2.png) > Displaying of labels of x-axis is broken now > > > Key: IGNITE-1614 > URL: https://issues.apache.org/jira/browse/IGNITE-1614 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: ig-1614-2.png, ig-1614.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1614) Displaying of labels of x-axis is broken now
[ https://issues.apache.org/jira/browse/IGNITE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1614: --- Attachment: ig-1614-2.png > Displaying of labels of x-axis is broken now > > > Key: IGNITE-1614 > URL: https://issues.apache.org/jira/browse/IGNITE-1614 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: ig-1614-2.png, ig-1614.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1614) Displaying of labels of x-axis is broken now
[ https://issues.apache.org/jira/browse/IGNITE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1614: --- Description: (was: Currently I'm observe that all labels are merged at the left side of the X-axis. They are unreadable.) > Displaying of labels of x-axis is broken now > > > Key: IGNITE-1614 > URL: https://issues.apache.org/jira/browse/IGNITE-1614 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: ig-1614.png > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1614) Displaying of labels of x-axis is broken now
[ https://issues.apache.org/jira/browse/IGNITE-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1614: --- Attachment: ig-1614.png > Displaying of labels of x-axis is broken now > > > Key: IGNITE-1614 > URL: https://issues.apache.org/jira/browse/IGNITE-1614 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Andrey Novikov > Fix For: ignite-1.5 > > Attachments: ig-1614.png > > > Currently I'm observe that all labels are merged at the left side of the > X-axis. > They are unreadable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1614) Displaying of labels of x-axis is broken now
Pavel Konstantinov created IGNITE-1614: -- Summary: Displaying of labels of x-axis is broken now Key: IGNITE-1614 URL: https://issues.apache.org/jira/browse/IGNITE-1614 Project: Ignite Issue Type: Sub-task Reporter: Pavel Konstantinov Assignee: Andrey Novikov Currently I'm observe that all labels are merged at the left side of the X-axis. They are unreadable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942906#comment-14942906 ] Pavel Konstantinov edited comment on IGNITE-1485 at 10/5/15 4:21 AM: - Currently we allow to save invalid metadata loaded from DB - metadata without key fields for store. The reason is the table in database had no key fields. We should not allow user to select such metadata for caches. We should somehow mark such metadata and make possible filter such metadata on metadata page. was (Author: pkonstantinov): Currently we allow to save invalid metadata - metadata without key fields for store. The reason is the table in database had no key fields. We should not allow user to select such metadata for caches. We should somehow mark such metadata and make possible filter such metadata on metadata page. > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942906#comment-14942906 ] Pavel Konstantinov edited comment on IGNITE-1485 at 10/5/15 4:18 AM: - Currently we allow to save invalid metadata - metadata without key fields for store. The reason is the table in database had no key fields. We should not allow user to select such metadata for caches. We should somehow mark such metadata and make possible filter such metadata on metadat page. was (Author: pkonstantinov): Currently we allow to save invalid metadata - metadata without key fields for store. The reason is the table in database had no key fields. We should not allow user to select such metadata for caches. We should somehow mark such metadata and make possibly filter such metadata on metadat page. > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942906#comment-14942906 ] Pavel Konstantinov edited comment on IGNITE-1485 at 10/5/15 4:18 AM: - Currently we allow to save invalid metadata - metadata without key fields for store. The reason is the table in database had no key fields. We should not allow user to select such metadata for caches. We should somehow mark such metadata and make possible filter such metadata on metadata page. was (Author: pkonstantinov): Currently we allow to save invalid metadata - metadata without key fields for store. The reason is the table in database had no key fields. We should not allow user to select such metadata for caches. We should somehow mark such metadata and make possible filter such metadata on metadat page. > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942906#comment-14942906 ] Pavel Konstantinov commented on IGNITE-1485: Currently we allow to save invalid metadata - metadata without key fields for store. The reason is the table in database had no key fields. We should not allow user to select such metadata for caches. We should somehow mark such metadata and make possibly filter such metadata on metadat page. > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942903#comment-14942903 ] Pavel Konstantinov commented on IGNITE-1485: Currently fields used for indexes are also included in not indexed fields group. This is wrong. We should not include they in not indexed fields. > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1485) Improve loading metadata from DB
[ https://issues.apache.org/jira/browse/IGNITE-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-1485: --- Description: (was: Currently fields used for indexes are also included in not indexed fields group. This is wrong. We should not include they in not indexed fields.) > Improve loading metadata from DB > > > Key: IGNITE-1485 > URL: https://issues.apache.org/jira/browse/IGNITE-1485 > Project: Ignite > Issue Type: Sub-task > Components: wizards >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm
[
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942638#comment-14942638
]
ASF GitHub Bot commented on IGNITE-429:
---
Github user murador closed the pull request at:
https://github.com/apache/ignite/pull/110
> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm
> and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-708) Need to remove background partition exchange
[ https://issues.apache.org/jira/browse/IGNITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942633#comment-14942633 ] ASF GitHub Bot commented on IGNITE-708: --- GitHub user murador opened a pull request: https://github.com/apache/ignite/pull/129 IGNITE-708: Remove refreshPartitions on ResendTimeoutObject. IGNITE-708: From what I could see, the refresh partition in case of timeout is redundant, since each node has a refresh partition which runs at regular intervals in the method body() of GridCachePartitionExchangeManager retrieved from the background process ExchangeWorker. Thus eliminating the refreshPartition in ResendTimeoutObject class should not have any impact on the operation, but an increase in performance when we avoid sending redundant message. You can merge this pull request into a Git repository by running: $ git pull https://github.com/murador/ignite IGNITE-708 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/129.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 #129 commit bfe23fb8eca05d67ec4c3e195c9a972616072c93 Author: murador Date: 2015-10-04T10:45:18Z Remove refreshPartitions on ResendTimeoutObject. > Need to remove background partition exchange > > > Key: IGNITE-708 > URL: https://issues.apache.org/jira/browse/IGNITE-708 > Project: Ignite > Issue Type: Task >Affects Versions: ignite-1.4 >Reporter: Yakov Zhdanov >Assignee: Gianfranco Murador >Priority: Blocker > Labels: datagrid > Fix For: ignite-1.5, ignite-1.6 > > > Now every node sends its partition map to cache coordinator (which is the > oldest node in topology) and coordinator spreads full partition map to every > node in topology. This happens for each cache separately. This seems to take > place even if there were no changes to local partition maps. Given we > guarantee communication message delivery this background process seems to be > an overkill. > Exchange should happen only if any changes took place. > After dynamic cache start has been introduced, we can have significant amount > of live caches at some point of app lifecycle and app may suffer from > background exchange which is obviously not a requirement (and may be never > has been the one). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-708) Need to remove background partition exchange
[ https://issues.apache.org/jira/browse/IGNITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942629#comment-14942629 ] ASF GitHub Bot commented on IGNITE-708: --- Github user murador closed the pull request at: https://github.com/apache/ignite/pull/86 > Need to remove background partition exchange > > > Key: IGNITE-708 > URL: https://issues.apache.org/jira/browse/IGNITE-708 > Project: Ignite > Issue Type: Task >Affects Versions: ignite-1.4 >Reporter: Yakov Zhdanov >Assignee: Gianfranco Murador >Priority: Blocker > Labels: datagrid > Fix For: ignite-1.5, ignite-1.6 > > > Now every node sends its partition map to cache coordinator (which is the > oldest node in topology) and coordinator spreads full partition map to every > node in topology. This happens for each cache separately. This seems to take > place even if there were no changes to local partition maps. Given we > guarantee communication message delivery this background process seems to be > an overkill. > Exchange should happen only if any changes took place. > After dynamic cache start has been introduced, we can have significant amount > of live caches at some point of app lifecycle and app may suffer from > background exchange which is obviously not a requirement (and may be never > has been the one). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm
[
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942618#comment-14942618
]
Gianfranco Murador commented on IGNITE-429:
---
Hello Chandresh,
the code has been written correctly,
can you please check these tips described by Anton ?
Regards, Gianfranco
2) Redundant newlines should be removed. At code and imports.
3) Newlines should be added where it necessary:
for example:
Map res = process(tuple);
collector.emit(new Values(res));
5) @Override should be located according to Coding Guidelines.
6) Javadoc sentences should be finished with dot.
> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm
> and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm
[
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianfranco Murador updated IGNITE-429:
--
Comment: was deleted
(was: Hello Chandresh,
the code has been written correctly,
can you please check these tips described by Anton ?
Regards, Gianfranco
2) Redundant newlines should be removed. At code and imports.
3) Newlines should be added where it necessary:
for example:
Map res = process(tuple);
collector.emit(new Values(res));
5) @Override should be located according to Coding Guidelines.
6) Javadoc sentences should be finished with dot.
)
> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm
> and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm
[
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942617#comment-14942617
]
Gianfranco Murador commented on IGNITE-429:
---
Hello Chandresh,
the code has been written correctly,
can you please check these tips described by Anton ?
Regards, Gianfranco
2) Redundant newlines should be removed. At code and imports.
3) Newlines should be added where it necessary:
for example:
Map res = process(tuple);
collector.emit(new Values(res));
5) @Override should be located according to Coding Guidelines.
6) Javadoc sentences should be finished with dot.
> Implement IgniteStormStreamer to stream data from Apache Storm
> --
>
> Key: IGNITE-429
> URL: https://issues.apache.org/jira/browse/IGNITE-429
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Chandresh Pancholi
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Apache Storm|https://storm.apache.org/] for more information.
> We should create {{IgniteStormStreamer}} which will consume tuples from Storm
> and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> - Convert/Intercept Storm tuples to Ignite data using an optional pluggable
> converter.
> - Specify the cache name for the Ignite cache to load data into.
> - Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
