[jira] [Commented] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

2015-09-20 Thread Gianfranco Murador (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877480#comment-14877480
 ] 

Gianfranco Murador commented on IGNITE-429:
---

Hello Chandresh,
how do you see the implementation is simple ( this is good ), but It does not 
take into account of some aspects that may not work in Ignite. As we have done 
in Kafka streamer is a good idea to create an ExecutorService to submit streams 
from apache storm (This improves performance) . You have to rely to a naming 
convention that must be declared with your solution, while it might be a good 
idea to create our bolt to filter results. I will make a new branch with all 
the changes, so you can make a new pull request. Still I am not very skilled 
with git :).
Regards, Gianfranco 

> 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] [Comment Edited] (IGNITE-429) Implement IgniteStormStreamer to stream data from Apache Storm

2015-09-20 Thread Gianfranco Murador (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14877480#comment-14877480
 ] 

Gianfranco Murador edited comment on IGNITE-429 at 9/20/15 11:51 AM:
-

Hello Chandresh,
 the implementation is simple ( this is good ), but It does not take into 
account of some aspects that may not work in Ignite. As we have done in Kafka 
streamer is a good idea to create an ExecutorService to submit streams from 
apache storm (This improves performance) . You have to rely to a naming 
convention that must be declared with your solution, while it might be a good 
idea to create our bolt to filter results. I will make a new branch with all 
the changes, so you can make a new pull request. Still I am not very skilled 
with git :).
Regards, Gianfranco 


was (Author: glutters):
Hello Chandresh,
how do you see the implementation is simple ( this is good ), but It does not 
take into account of some aspects that may not work in Ignite. As we have done 
in Kafka streamer is a good idea to create an ExecutorService to submit streams 
from apache storm (This improves performance) . You have to rely to a naming 
convention that must be declared with your solution, while it might be a good 
idea to create our bolt to filter results. I will make a new branch with all 
the changes, so you can make a new pull request. Still I am not very skilled 
with git :).
Regards, Gianfranco 

> 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

2015-09-20 Thread Gianfranco Murador (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14899944#comment-14899944
 ] 

Gianfranco Murador commented on IGNITE-429:
---

Hi Chandresh, 
  please, look here 
https://github.com/murador/ignite/tree/IGNITE-429/modules/storm/src. Now, We 
need to create unit test.Let me know if you find problems with the proposed 
solution .

> 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] [Resolved] (IGNITE-1502) Move web console to HTTPS protocol.

2015-09-20 Thread Andrey Novikov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov resolved IGNITE-1502.

Resolution: Fixed

> Move web console to HTTPS protocol.
> ---
>
> Key: IGNITE-1502
> URL: https://issues.apache.org/jira/browse/IGNITE-1502
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Nikita Ivanov
>Assignee: Alexey Kuznetsov
>
> I think it makes sense to move to HTTPS since we are dealing with potentially 
> sensitive user information. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (IGNITE-1502) Move web console to HTTPS protocol.

2015-09-20 Thread Andrey Novikov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov updated IGNITE-1502:
---
Issue Type: Sub-task  (was: New Feature)
Parent: IGNITE-843

> Move web console to HTTPS protocol.
> ---
>
> Key: IGNITE-1502
> URL: https://issues.apache.org/jira/browse/IGNITE-1502
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Nikita Ivanov
>Assignee: Alexey Kuznetsov
>
> I think it makes sense to move to HTTPS since we are dealing with potentially 
> sensitive user information. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (IGNITE-1484) Allow to store configuration in Google Datastore.

2015-09-20 Thread Andrey Novikov (JIRA)

 [ 
https://issues.apache.org/jira/browse/IGNITE-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Novikov updated IGNITE-1484:
---
Issue Type: Sub-task  (was: New Feature)
Parent: IGNITE-843

> Allow to store configuration in Google Datastore.
> -
>
> Key: IGNITE-1484
> URL: https://issues.apache.org/jira/browse/IGNITE-1484
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI
>Reporter: Nikita Ivanov
>Assignee: Alexey Kuznetsov
>
> It would be very convenient to store a configuration (e.g. in Google 
> Datastore) and come back to it later. We need to introduce a notion of new 
> configuration (with a name) and ability to "load" previously saved 
> configuration by name.
> We should store these outside of local database so that it would survive 
> restarts and DB updates. Google Datastore is good tech to use here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (IGNITE-815) Reactive Streams Compatibility

2015-09-20 Thread Suminda Dharmasena (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14900163#comment-14900163
 ] 

Suminda Dharmasena commented on IGNITE-815:
---

Data streamer, continuous queries, 

> Reactive Streams Compatibility
> --
>
> Key: IGNITE-815
> URL: https://issues.apache.org/jira/browse/IGNITE-815
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Suminda Dharmasena
>
> http://www.reactive-streams.org/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)