[jira] [Commented] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized
[
https://issues.apache.org/jira/browse/IGNITE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724318#comment-14724318
]
Raúl Kripalani commented on IGNITE-1238:
Hey [~vkulichenko], I think I could take this ticket if you're not working on
it. Let me know.
Raúl.
> Joining node should be discarded in case discovery exchange data can't be
> deserialized
> --
>
> Key: IGNITE-1238
> URL: https://issues.apache.org/jira/browse/IGNITE-1238
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Valentin Kulichenko
>Priority: Critical
> Fix For: ignite-1.4
>
>
> Currently a node will join even if unmarshalling fails (see
> {{TcpDiscoverySpi.onExchange()}} method, which can cause unexpected
> behaviour. For example, a continuous query listener is not deployed on some
> nodes in topology. Everything works, but some updates are lost. We should
> discard the node in this case and give a good error message to user with
> information on how to fix it properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1075) IgniteDataStreamer doesn't throw an exception if there are no data nodes
[
https://issues.apache.org/jira/browse/IGNITE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724321#comment-14724321
]
Raúl Kripalani commented on IGNITE-1075:
Hey [~vkulichenko], I could take this ticket if you're not working on it.
Raúl.
> IgniteDataStreamer doesn't throw an exception if there are no data nodes
>
>
> Key: IGNITE-1075
> URL: https://issues.apache.org/jira/browse/IGNITE-1075
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Priority: Critical
> Labels: Usability
>
> If you call {{addData}} method, but there are no data nodes, you will never
> know about it. Looks like it is returned in a future, but it's
> counterintuitive to call it on each operation just to check for exception.
> Probably we should print out these errors in logs as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized
[
https://issues.apache.org/jira/browse/IGNITE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani reassigned IGNITE-1238:
--
Assignee: Raúl Kripalani (was: Valentin Kulichenko)
> Joining node should be discarded in case discovery exchange data can't be
> deserialized
> --
>
> Key: IGNITE-1238
> URL: https://issues.apache.org/jira/browse/IGNITE-1238
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Raúl Kripalani
>Priority: Critical
> Fix For: ignite-1.4
>
>
> Currently a node will join even if unmarshalling fails (see
> {{TcpDiscoverySpi.onExchange()}} method, which can cause unexpected
> behaviour. For example, a continuous query listener is not deployed on some
> nodes in topology. Everything works, but some updates are lost. We should
> discard the node in this case and give a good error message to user with
> information on how to fix it properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1238) Joining node should be discarded in case discovery exchange data can't be deserialized
[
https://issues.apache.org/jira/browse/IGNITE-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724415#comment-14724415
]
Raúl Kripalani commented on IGNITE-1238:
Hey Valentin, do we have a test case that demonstrates what's wrong? If not,
could you give me a hint on how to build such a test case? I think that would
be the starting point. Thanks.
> Joining node should be discarded in case discovery exchange data can't be
> deserialized
> --
>
> Key: IGNITE-1238
> URL: https://issues.apache.org/jira/browse/IGNITE-1238
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Raúl Kripalani
>Priority: Critical
> Fix For: ignite-1.4
>
>
> Currently a node will join even if unmarshalling fails (see
> {{TcpDiscoverySpi.onExchange()}} method, which can cause unexpected
> behaviour. For example, a continuous query listener is not deployed on some
> nodes in topology. Everything works, but some updates are lost. We should
> discard the node in this case and give a good error message to user with
> information on how to fix it properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
Raúl Kripalani created IGNITE-1370:
--
Summary: StreamTupleExtractor should allow extracting multiple
tuples from a single event
Key: IGNITE-1370
URL: https://issues.apache.org/jira/browse/IGNITE-1370
Project: Ignite
Issue Type: Improvement
Components: streaming
Affects Versions: ignite-1.4
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani
Currently the {{StreamTupleExtractor}} interface contains a single method:
{code}
public Map.Entry extract(T msg);
{code}
Which only allows extracting a single Entry from an incoming event.
In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729884#comment-14729884
]
Raúl Kripalani commented on IGNITE-1370:
There are two options off the top of my head:
# API-breaking one => modifying StreamTupleExtractor to add a second method
returning a Map and a method {{boolean supportsMultiple()}} for users to
implement, so that Streamers can query the extractor to know which method to
invoke.
# A new class {{StreamMultipleTupleExtractor}} that Streamers supporting this
functionality can use. It would require streamers to hold two fields:
singleTupleExtractor or multipleTupleExtractor (for example), for users to be
able to set either.
> StreamTupleExtractor should allow extracting multiple tuples from a single
> event
>
>
> Key: IGNITE-1370
> URL: https://issues.apache.org/jira/browse/IGNITE-1370
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
>
> Currently the {{StreamTupleExtractor}} interface contains a single method:
> {code}
> public Map.Entry extract(T msg);
> {code}
> Which only allows extracting a single Entry from an incoming event.
> In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14729884#comment-14729884
]
Raúl Kripalani edited comment on IGNITE-1370 at 9/3/15 10:04 PM:
-
There are two options off the top of my head:
# API-breaking one => modifying StreamTupleExtractor to add a second method
returning a Map and a method {{boolean supportsMultiple()}} for users to
implement, so that Streamers can query the extractor to know which method to
invoke.
# A new class {{StreamMultipleTupleExtractor}} that Streamers supporting this
functionality can use. It would require streamers to hold two fields:
singleTupleExtractor or multipleTupleExtractor (for example), for users to be
able to set either.
was (Author: raulvk):
There are two options off the top of my head:
# API-breaking one => modifying StreamTupleExtractor to add a second method
returning a Map and a method {{boolean supportsMultiple()}} for users to
implement, so that Streamers can query the extractor to know which method to
invoke.
# A new class {{StreamMultipleTupleExtractor}} that Streamers supporting this
functionality can use. It would require streamers to hold two fields:
singleTupleExtractor or multipleTupleExtractor (for example), for users to be
able to set either.
> StreamTupleExtractor should allow extracting multiple tuples from a single
> event
>
>
> Key: IGNITE-1370
> URL: https://issues.apache.org/jira/browse/IGNITE-1370
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
>
> Currently the {{StreamTupleExtractor}} interface contains a single method:
> {code}
> public Map.Entry extract(T msg);
> {code}
> Which only allows extracting a single Entry from an incoming event.
> In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736683#comment-14736683
]
Raúl Kripalani commented on IGNITE-1370:
Hey Valentin,
Sorry for the delay. Yes, we can definitely do that. Currently I validate that
both are not null, but we can definitely add the extra validation if both are
set.
The reason why I wouldn't deprecate single altogether is that multiple forces
the user to create a Map. If you know your message will only ever return 1
tuple, creating a Map is extra overhead and leads to unnecessary GC.
However, I think we should rename StreamTupleExtractor to
Stream*Single*TupleExtractor. To do this without breaking the API I suggest we
perform the rename and then create StreamTupleExtractor again extending the new
StreamSingleTupleExtractor and marking it as @Deprecated.
What do you think?
> StreamTupleExtractor should allow extracting multiple tuples from a single
> event
>
>
> Key: IGNITE-1370
> URL: https://issues.apache.org/jira/browse/IGNITE-1370
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
>
> Currently the {{StreamTupleExtractor}} interface contains a single method:
> {code}
> public Map.Entry extract(T msg);
> {code}
> Which only allows extracting a single Entry from an incoming event.
> In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738440#comment-14738440
]
Raúl Kripalani commented on IGNITE-1370:
If you duplicate them, the user won't be able to use both interfaces
interchangeably.
Hence, I think extension is more comfortable for the user at this point. We
also want to rename the field in {{extractor}} field in {{StreamAdapter}} to
{{singleTupleExtractor}}, creating new getters and setters but keeping the old
ones {{getExtractor}} and {{setExtractor}} and marking them as {{@Deprecated}}.
Raúl.
> StreamTupleExtractor should allow extracting multiple tuples from a single
> event
>
>
> Key: IGNITE-1370
> URL: https://issues.apache.org/jira/browse/IGNITE-1370
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
>
> Currently the {{StreamTupleExtractor}} interface contains a single method:
> {code}
> public Map.Entry extract(T msg);
> {code}
> Which only allows extracting a single Entry from an incoming event.
> In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-535) Implement IgniteMqttStreamer to stream data from MQTT
[
https://issues.apache.org/jira/browse/IGNITE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14744467#comment-14744467
]
Raúl Kripalani commented on IGNITE-535:
---
Working on this. It'll be ready this week.
> Implement IgniteMqttStreamer to stream data from MQTT
> -
>
> Key: IGNITE-535
> URL: https://issues.apache.org/jira/browse/IGNITE-535
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Raúl Kripalani
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [MQTT|http://mqtt.org/] site for more info.
> We should create {{IgniteMqttStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert MQTT messages to Ignite data using an optional pluggable converter.
> If not provided, we should have some default mechanism.
> * 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-1371) Key-Value store (like Cassandra) as CacheStore
[ https://issues.apache.org/jira/browse/IGNITE-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14899917#comment-14899917 ] Raúl Kripalani commented on IGNITE-1371: Hi [~aboudnik], Just wondering if you were working on this ticket. Which DB are you integrating? If we aim to integrate several DBs, my guess is that we'll need one module for each (unless we use an abstraction like Spring Data, but that would slow things down). Is it ok to scope this ticket to Cassandra only? Thanks, Raúl. > Key-Value store (like Cassandra) as CacheStore > -- > > Key: IGNITE-1371 > URL: https://issues.apache.org/jira/browse/IGNITE-1371 > Project: Ignite > Issue Type: New Feature > Components: cache >Reporter: Alexandre Boudnik >Assignee: Alexandre Boudnik > Original Estimate: 504h > Remaining Estimate: 504h > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-535) Implement IgniteMqttStreamer to stream data from MQTT
[
https://issues.apache.org/jira/browse/IGNITE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani resolved IGNITE-535.
---
Resolution: Fixed
Fix Version/s: ignite-1.5
Merged into master in 88acd318b84ce3bff8c061bb34718e0e5f7127fb.
> Implement IgniteMqttStreamer to stream data from MQTT
> -
>
> Key: IGNITE-535
> URL: https://issues.apache.org/jira/browse/IGNITE-535
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [MQTT|http://mqtt.org/] site for more info.
> We should create {{IgniteMqttStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert MQTT messages to Ignite data using an optional pluggable converter.
> If not provided, we should have some default mechanism.
> * 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] [Created] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles
Raúl Kripalani created IGNITE-1527: -- Summary: Add OSGi manifest headers to all ignite-core + basic bundles Key: IGNITE-1527 URL: https://issues.apache.org/jira/browse/IGNITE-1527 Project: Ignite Issue Type: Sub-task Components: general Reporter: Raúl Kripalani Assignee: Raúl Kripalani And make sure they interoperate properly with each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1528) Support client mode with Ignite OSGi
Raúl Kripalani created IGNITE-1528: -- Summary: Support client mode with Ignite OSGi Key: IGNITE-1528 URL: https://issues.apache.org/jira/browse/IGNITE-1528 Project: Ignite Issue Type: Sub-task Components: general Reporter: Raúl Kripalani Assignee: Raúl Kripalani -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1530) Support Zero Deployment with Ignite OSGi server mode
Raúl Kripalani created IGNITE-1530: -- Summary: Support Zero Deployment with Ignite OSGi server mode Key: IGNITE-1530 URL: https://issues.apache.org/jira/browse/IGNITE-1530 Project: Ignite Issue Type: Sub-task Components: general Reporter: Raúl Kripalani Assignee: Raúl Kripalani -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1529) Support server mode with Ignite OSGi without Zero Deployment
Raúl Kripalani created IGNITE-1529: -- Summary: Support server mode with Ignite OSGi without Zero Deployment Key: IGNITE-1529 URL: https://issues.apache.org/jira/browse/IGNITE-1529 Project: Ignite Issue Type: Sub-task Components: general Reporter: Raúl Kripalani Assignee: Raúl Kripalani -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1531) Allow users to create and start Ignite configurations via OSGi Managed Service Factories
Raúl Kripalani created IGNITE-1531: -- Summary: Allow users to create and start Ignite configurations via OSGi Managed Service Factories Key: IGNITE-1531 URL: https://issues.apache.org/jira/browse/IGNITE-1531 Project: Ignite Issue Type: Sub-task Components: general Reporter: Raúl Kripalani Assignee: Raúl Kripalani -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1529) Support server mode with Ignite OSGi without Zero Deployment
[ https://issues.apache.org/jira/browse/IGNITE-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1529: --- Description: Server mode means replication of user classes. Design a way for allow user bundles to contribute classes to ignite-core, without using DynamicImport-Package: * > Support server mode with Ignite OSGi without Zero Deployment > > > Key: IGNITE-1529 > URL: https://issues.apache.org/jira/browse/IGNITE-1529 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > > Server mode means replication of user classes. Design a way for allow user > bundles to contribute classes to ignite-core, without using > DynamicImport-Package: * -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-815) Reactive Streams Compatibility
[ https://issues.apache.org/jira/browse/IGNITE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909181#comment-14909181 ] Raúl Kripalani commented on IGNITE-815: --- Community shared their ideas on a mailing list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/Brainstorming-about-Reactive-Streams-td3346.html. [~lalitj] is this something you'd like to help us with? We can work together if you'd like. I didn't see negative feedback around using RxJava 1.0 + Reactive Streams adapter for now, to later switch to RxJava 2.0 with native RS support. So let's go in this direction. > 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)
[jira] [Created] (IGNITE-1554) igniterouter scripts are not working
Raúl Kripalani created IGNITE-1554:
--
Summary: igniterouter scripts are not working
Key: IGNITE-1554
URL: https://issues.apache.org/jira/browse/IGNITE-1554
Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: ignite-1.4
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani
Fix For: ignite-1.5
Executing the {{igniterouter}} script fails with:
{code}
Error: Could not find or load main class
org.apache.ignite.client.router.impl.GridRouterCommandLineStartup
{code}
Since a refactoring in commit b88a1012e9031b760193179463ce852032c2e334.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1554) igniterouter scripts are not working
[
https://issues.apache.org/jira/browse/IGNITE-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani resolved IGNITE-1554.
Resolution: Fixed
> igniterouter scripts are not working
>
>
> Key: IGNITE-1554
> URL: https://issues.apache.org/jira/browse/IGNITE-1554
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> Executing the {{igniterouter}} script fails with:
> {code}
> Error: Could not find or load main class
> org.apache.ignite.client.router.impl.GridRouterCommandLineStartup
> {code}
> Since a refactoring in commit b88a1012e9031b760193179463ce852032c2e334.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1554) igniterouter scripts are not working
[
https://issues.apache.org/jira/browse/IGNITE-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14909187#comment-14909187
]
Raúl Kripalani commented on IGNITE-1554:
Fixed in ignite-1.4.1 but missing the fix version in JIRA.
> igniterouter scripts are not working
>
>
> Key: IGNITE-1554
> URL: https://issues.apache.org/jira/browse/IGNITE-1554
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: ignite-1.5
>
>
> Executing the {{igniterouter}} script fails with:
> {code}
> Error: Could not find or load main class
> org.apache.ignite.client.router.impl.GridRouterCommandLineStartup
> {code}
> Since a refactoring in commit b88a1012e9031b760193179463ce852032c2e334.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-815) Reactive Streams Compatibility
[
https://issues.apache.org/jira/browse/IGNITE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933463#comment-14933463
]
Raúl Kripalani commented on IGNITE-815:
---
Hey [~lalitj], I had a look at the notes. Detailed and referenced, excellent!
Do you have an account in the ASF Wiki? If not, please create one and ping the
dev@ mailing list so someone can give you write permission.
My idea for the 'reactive' module consisted in offering many fluent wrappers:
probably one per Ignite functionality we want to support with reactive. For
example, for ContinuousQueries:
{code}
ContinuousQuery contQuery = new ContinuousQuery<>();
// set up the continuous query
// ...
contQuery = IgniteReactive.wrapContinuousQuery(contQuery);// this would
return an object of a class extending ContinuousQuery and providing a
toObservable method
cache.query(contQuery);
contQuery.toObservable().subscribe(...);
{code}
(sorry but I'm using RxJava concepts as I'm more familiar with those).
What do you think?
Raúl.
> 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)
[jira] [Comment Edited] (IGNITE-815) Reactive Streams Compatibility
[
https://issues.apache.org/jira/browse/IGNITE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933463#comment-14933463
]
Raúl Kripalani edited comment on IGNITE-815 at 9/28/15 3:43 PM:
Hey [~lalitj], I had a look at the notes. Detailed and referenced, excellent!
Do you have an account in the ASF Wiki? If not, please create one and ping the
dev@ mailing list so someone can give you write permission.
My idea for the 'reactive' module consisted in offering many fluent wrappers:
probably one per Ignite functionality we want to support with reactive. For
example, for ContinuousQueries:
{code}
ContinuousQuery contQuery1 = new ContinuousQuery<>();
ContinuousQuery contQuery2 = new ContinuousQuery<>();
// set up the continuous queries
// ...
contQuery1 = IgniteReactive.wrapContinuousQuery(contQuery1);// this would
return an object of a class extending ContinuousQuery and providing a
toObservable method
contQuery2 = IgniteReactive.wrapContinuousQuery(contQuery2);
cache.query(contQuery1);
cache.query(contQuery2);
contQuery1.toObservable()
.merge(contQuery2.toObservable())
.subscribe(...);
{code}
(sorry but I'm using RxJava concepts as I'm more familiar with those).
What do you think?
Raúl.
was (Author: raulvk):
Hey [~lalitj], I had a look at the notes. Detailed and referenced, excellent!
Do you have an account in the ASF Wiki? If not, please create one and ping the
dev@ mailing list so someone can give you write permission.
My idea for the 'reactive' module consisted in offering many fluent wrappers:
probably one per Ignite functionality we want to support with reactive. For
example, for ContinuousQueries:
{code}
ContinuousQuery contQuery = new ContinuousQuery<>();
// set up the continuous query
// ...
contQuery = IgniteReactive.wrapContinuousQuery(contQuery);// this would
return an object of a class extending ContinuousQuery and providing a
toObservable method
cache.query(contQuery);
contQuery.toObservable().subscribe(...);
{code}
(sorry but I'm using RxJava concepts as I'm more familiar with those).
What do you think?
Raúl.
> 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)
[jira] [Updated] (IGNITE-1270) OSGi support for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1270: --- Fix Version/s: ignite-1.5 > OSGi support for Ignite > --- > > Key: IGNITE-1270 > URL: https://issues.apache.org/jira/browse/IGNITE-1270 > Project: Ignite > Issue Type: New Feature > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: ignite-1.5 > > > Basics for a first iteration: > * Manifest creation for all Java-based modules. > * Apache Karaf features file to facilitate deployment (along with > dependencies). > Future: > * Support peer class-loading. > * Potentially support remote 3rd dependency class-loading for Apache Karaf > (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1528) Support client mode with Ignite OSGi
[ https://issues.apache.org/jira/browse/IGNITE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1528: --- Fix Version/s: ignite-1.5 > Support client mode with Ignite OSGi > > > Key: IGNITE-1528 > URL: https://issues.apache.org/jira/browse/IGNITE-1528 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: ignite-1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles
[ https://issues.apache.org/jira/browse/IGNITE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1527: --- Fix Version/s: ignite-1.5 > Add OSGi manifest headers to all ignite-core + basic bundles > > > Key: IGNITE-1527 > URL: https://issues.apache.org/jira/browse/IGNITE-1527 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: ignite-1.5 > > > And make sure they interoperate properly with each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-534) Implement IgniteJmsStreamer to stream data from a JMS broker like ActiveMQ
[
https://issues.apache.org/jira/browse/IGNITE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani updated IGNITE-534:
--
Fix Version/s: ignite-1.4
> Implement IgniteJmsStreamer to stream data from a JMS broker like ActiveMQ
> --
>
> Key: IGNITE-534
> URL: https://issues.apache.org/jira/browse/IGNITE-534
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Valentin Kulichenko
> Fix For: ignite-1.4
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> We should create {{IgniteJmsStreamer}} which will consume messages from a
> given queue or topic of a JMS broker and stream them into Ignite caches.
> Even though we'll use AMQ for testing, this streamer should be
> implementation-agnostic and only use JMS constructs where possible.
> See [Apache ActiveMQ|http://activemq.apache.org/] for more information.
> More details to follow, but to the least we should be able to:
> * Convert a JMS message to Ignite data using an optional pluggable converter.
> If not provided, we should have some default mechanism.
> * 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] [Created] (IGNITE-1747) Fix code style issues in MQTT
Raúl Kripalani created IGNITE-1747: -- Summary: Fix code style issues in MQTT Key: IGNITE-1747 URL: https://issues.apache.org/jira/browse/IGNITE-1747 Project: Ignite Issue Type: Improvement Components: streaming Affects Versions: ignite-1.4 Reporter: Raúl Kripalani Assignee: Raúl Kripalani Fix For: 1.5 Coding guidelines have been updated/corrected in the last weeks. See discussion here: http://apache-ignite-developers.2346864.n4.nabble.com/Coding-Guidelines-zookeeper-IP-finder-and-mqtt-streamer-td3542.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1747) Fix code style issues and Javadoc in MQTT Streamer
[ https://issues.apache.org/jira/browse/IGNITE-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1747: --- Summary: Fix code style issues and Javadoc in MQTT Streamer (was: Fix code style issues in MQTT) > Fix code style issues and Javadoc in MQTT Streamer > -- > > Key: IGNITE-1747 > URL: https://issues.apache.org/jira/browse/IGNITE-1747 > Project: Ignite > Issue Type: Improvement > Components: streaming >Affects Versions: ignite-1.4 >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > Coding guidelines have been updated/corrected in the last weeks. See > discussion here: > http://apache-ignite-developers.2346864.n4.nabble.com/Coding-Guidelines-zookeeper-IP-finder-and-mqtt-streamer-td3542.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1789) Data Snapshots for Ignite caches
Raúl Kripalani created IGNITE-1789: -- Summary: Data Snapshots for Ignite caches Key: IGNITE-1789 URL: https://issues.apache.org/jira/browse/IGNITE-1789 Project: Ignite Issue Type: New Feature Components: cache Reporter: Raúl Kripalani There was a discussion in the dev forum about Data Snapshots in Ignite as a way to obtain a consistent and "frozen" view of one or multiple caches in order to execute a set of SQL queries, distributed closures, map reduce, etc. without having to worry about data slippage (or moving data). The discussion is here: http://apache-ignite-developers.2346864.n4.nabble.com/Data-Snapshots-in-Ignite-td4183.html and we still need to mature the idea, but several users chimed in and considered it interesting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1790) Implement an Apache Camel Data Streamer
Raúl Kripalani created IGNITE-1790: -- Summary: Implement an Apache Camel Data Streamer Key: IGNITE-1790 URL: https://issues.apache.org/jira/browse/IGNITE-1790 Project: Ignite Issue Type: New Feature Components: streaming Reporter: Raúl Kripalani Assignee: Raúl Kripalani Fix For: 1.5 An Apache Camel data streamer would make it possible for a user to use any of Camel's [150+ adapters/components|http://camel.apache.org/components.html] to consume data from the outside world and feed it into an Ignite cache. SOAP, REST, HTTP, WebSockets, FTP, File, XMPP, SMPP, POP3, IMAP, TCP, etc. This data streamer will instantiate a Camel consumer endpoint, it'll apply the user-specified StreamTransformer to the incoming Exchange and it'll add the result to the data streamer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1747) Fix code style issues and Javadoc in MQTT Streamer
[ https://issues.apache.org/jira/browse/IGNITE-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1747: --- Priority: Minor (was: Major) > Fix code style issues and Javadoc in MQTT Streamer > -- > > Key: IGNITE-1747 > URL: https://issues.apache.org/jira/browse/IGNITE-1747 > Project: Ignite > Issue Type: Improvement > Components: streaming >Affects Versions: ignite-1.4 >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani >Priority: Minor > Fix For: 1.5 > > > Coding guidelines have been updated/corrected in the last weeks. See > discussion here: > http://apache-ignite-developers.2346864.n4.nabble.com/Coding-Guidelines-zookeeper-IP-finder-and-mqtt-streamer-td3542.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1747) Fix code style issues and Javadoc in MQTT Streamer
[ https://issues.apache.org/jira/browse/IGNITE-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1747: --- Affects Version/s: (was: ignite-1.4) 1.5 > Fix code style issues and Javadoc in MQTT Streamer > -- > > Key: IGNITE-1747 > URL: https://issues.apache.org/jira/browse/IGNITE-1747 > Project: Ignite > Issue Type: Improvement > Components: streaming >Affects Versions: 1.5 >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani >Priority: Minor > Fix For: 1.5 > > > Coding guidelines have been updated/corrected in the last weeks. See > discussion here: > http://apache-ignite-developers.2346864.n4.nabble.com/Coding-Guidelines-zookeeper-IP-finder-and-mqtt-streamer-td3542.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1810) Upgrade ignite-aws dependencies (HttpClient and AWS SDK)
Raúl Kripalani created IGNITE-1810: -- Summary: Upgrade ignite-aws dependencies (HttpClient and AWS SDK) Key: IGNITE-1810 URL: https://issues.apache.org/jira/browse/IGNITE-1810 Project: Ignite Issue Type: Improvement Components: aws Reporter: Raúl Kripalani Assignee: Raúl Kripalani Fix For: 1.5 We need to upgrade the HttpClient and AWS SDK dependencies in ignite-aws. They are very old: * AWS SDK 1.3.21.1 => 1.10.29 * HttpClient 4.2.3 => 4.5.1 * HttpCore 4.2.3 => 4.4.3 These upgrades are needed by the OSGi integration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1812) Create a Maven BOM for Apache Ignite
Raúl Kripalani created IGNITE-1812:
--
Summary: Create a Maven BOM for Apache Ignite
Key: IGNITE-1812
URL: https://issues.apache.org/jira/browse/IGNITE-1812
Project: Ignite
Issue Type: New Feature
Reporter: Raúl Kripalani
Assignee: Raúl Kripalani
Priority: Minor
In Maven, a
[BOM|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies]
== "Bill of Materials".
BOMs provide an improved, short and safe way for users to import modules
without having to reference the Ignite version over and over again.
It allows the user to add all of Ignite's modules into their
{{}} section within a single dependency import. They
are consequently able to reference modules without specifying the Ignite
version:
{code}
org.apache.ignite
ignite-indexing
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999038#comment-14999038
]
Raúl Kripalani commented on IGNITE-1370:
Yes, but in compliance with [SemVer 2.0|http://semver.org/], we are not allowed
to break APIs in minor versions.
We could consider this for Ignite 2.0.
> StreamTupleExtractor should allow extracting multiple tuples from a single
> event
>
>
> Key: IGNITE-1370
> URL: https://issues.apache.org/jira/browse/IGNITE-1370
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: 1.5
>
>
> Currently the {{StreamTupleExtractor}} interface contains a single method:
> {code}
> public Map.Entry extract(T msg);
> {code}
> Which only allows extracting a single Entry from an incoming event.
> In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1370) StreamTupleExtractor should allow extracting multiple tuples from a single event
[
https://issues.apache.org/jira/browse/IGNITE-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999040#comment-14999040
]
Raúl Kripalani commented on IGNITE-1370:
You can use the instanceof operator or Class.isAssignableFrom() to determine
the type.
> StreamTupleExtractor should allow extracting multiple tuples from a single
> event
>
>
> Key: IGNITE-1370
> URL: https://issues.apache.org/jira/browse/IGNITE-1370
> Project: Ignite
> Issue Type: Improvement
> Components: streaming
>Affects Versions: ignite-1.4
>Reporter: Raúl Kripalani
>Assignee: Raúl Kripalani
> Fix For: 1.5
>
>
> Currently the {{StreamTupleExtractor}} interface contains a single method:
> {code}
> public Map.Entry extract(T msg);
> {code}
> Which only allows extracting a single Entry from an incoming event.
> In real life, it could be that an event contains multiple entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles and Karaf features
[ https://issues.apache.org/jira/browse/IGNITE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1527: --- Summary: Add OSGi manifest headers to all ignite-core + basic bundles and Karaf features (was: Add OSGi manifest headers to all ignite-core + basic bundles) > Add OSGi manifest headers to all ignite-core + basic bundles and Karaf > features > --- > > Key: IGNITE-1527 > URL: https://issues.apache.org/jira/browse/IGNITE-1527 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > And make sure they interoperate properly with each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1885) Ignite ZooKeeper: Upgrade Curator to 2.9.1
Raúl Kripalani created IGNITE-1885: -- Summary: Ignite ZooKeeper: Upgrade Curator to 2.9.1 Key: IGNITE-1885 URL: https://issues.apache.org/jira/browse/IGNITE-1885 Project: Ignite Issue Type: Improvement Components: ignite-zookeeper Affects Versions: ignite-1.4 Reporter: Raúl Kripalani Assignee: Raúl Kripalani Fix For: 1.5 Upgrade the Apache Curator dependencies to 2.9.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1885) Ignite ZooKeeper: Upgrade Curator to 2.9.1
[ https://issues.apache.org/jira/browse/IGNITE-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani resolved IGNITE-1885. Resolution: Fixed > Ignite ZooKeeper: Upgrade Curator to 2.9.1 > -- > > Key: IGNITE-1885 > URL: https://issues.apache.org/jira/browse/IGNITE-1885 > Project: Ignite > Issue Type: Improvement > Components: ignite-zookeeper >Affects Versions: ignite-1.4 >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > Upgrade the Apache Curator dependencies to 2.9.1. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1790) Implement an Apache Camel Data Streamer
[ https://issues.apache.org/jira/browse/IGNITE-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011543#comment-15011543 ] Raúl Kripalani commented on IGNITE-1790: #1 Done. #2 Agree but it's a bit late. The A#notNullOrEmpty method was introduced in 1.4 and has already been used in 4 other components. Moreover, the Kafka streamer (which I based my first streamer on) also threw an IAE in this same case. I don't think it's important. From the technical perspective it may be somewhat inaccurate to use IAE, but from the functional perspective it more correct than ISA. #3 Yes, it makes sense to refactor StreamAdapter to add a start() method. We can open a ticket for 1.6. #4 It's not so important, as the element that actually important is the consumer. This is the one that'll bind to ports, consume files, etc. And it's last in the start chain. However, I have hardened the logic to stop all services in case the init fails. That way we're more atomic. Tests: #1 Done. These annotations are JUnit 4. #2 Done. > Implement an Apache Camel Data Streamer > --- > > Key: IGNITE-1790 > URL: https://issues.apache.org/jira/browse/IGNITE-1790 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > An Apache Camel data streamer would make it possible for a user to use any of > Camel's [150+ adapters/components|http://camel.apache.org/components.html] to > consume data from the outside world and feed it into an Ignite cache. > SOAP, REST, HTTP, WebSockets, FTP, File, XMPP, SMPP, POP3, IMAP, TCP, etc. > This data streamer will instantiate a Camel consumer endpoint, it'll apply > the user-specified StreamTransformer to the incoming Exchange and it'll add > the result to the data streamer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1790) Implement an Apache Camel Data Streamer
[ https://issues.apache.org/jira/browse/IGNITE-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011582#comment-15011582 ] Raúl Kripalani commented on IGNITE-1790: Documentation pending. > Implement an Apache Camel Data Streamer > --- > > Key: IGNITE-1790 > URL: https://issues.apache.org/jira/browse/IGNITE-1790 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > An Apache Camel data streamer would make it possible for a user to use any of > Camel's [150+ adapters/components|http://camel.apache.org/components.html] to > consume data from the outside world and feed it into an Ignite cache. > SOAP, REST, HTTP, WebSockets, FTP, File, XMPP, SMPP, POP3, IMAP, TCP, etc. > This data streamer will instantiate a Camel consumer endpoint, it'll apply > the user-specified StreamTransformer to the incoming Exchange and it'll add > the result to the data streamer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1530) Ignite OSGi: Support Peer Classloading (Zero Deployment)
[ https://issues.apache.org/jira/browse/IGNITE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1530: --- Summary: Ignite OSGi: Support Peer Classloading (Zero Deployment) (was: Support Zero Deployment with Ignite OSGi server mode) > Ignite OSGi: Support Peer Classloading (Zero Deployment) > > > Key: IGNITE-1530 > URL: https://issues.apache.org/jira/browse/IGNITE-1530 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1270) Basic OSGi support for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1270: --- Summary: Basic OSGi support for Ignite (was: OSGi support for Ignite) > Basic OSGi support for Ignite > - > > Key: IGNITE-1270 > URL: https://issues.apache.org/jira/browse/IGNITE-1270 > Project: Ignite > Issue Type: New Feature > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > Basics for a first iteration: > * Manifest creation for all Java-based modules. > * Apache Karaf features file to facilitate deployment (along with > dependencies). > Future: > * Support peer class-loading. > * Potentially support remote 3rd dependency class-loading for Apache Karaf > (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1530) Ignite OSGi: Support Peer Classloading (Zero Deployment)
[ https://issues.apache.org/jira/browse/IGNITE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1530: --- Issue Type: New Feature (was: Sub-task) Parent: (was: IGNITE-1270) > Ignite OSGi: Support Peer Classloading (Zero Deployment) > > > Key: IGNITE-1530 > URL: https://issues.apache.org/jira/browse/IGNITE-1530 > Project: Ignite > Issue Type: New Feature > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1529) Support server mode with Ignite OSGi without Peer Classloading
[ https://issues.apache.org/jira/browse/IGNITE-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1529: --- Summary: Support server mode with Ignite OSGi without Peer Classloading (was: Support server mode with Ignite OSGi without Zero Deployment) > Support server mode with Ignite OSGi without Peer Classloading > -- > > Key: IGNITE-1529 > URL: https://issues.apache.org/jira/browse/IGNITE-1529 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > > Server mode means replication of user classes. Design a way for allow user > bundles to contribute classes to ignite-core, without using > DynamicImport-Package: * -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1531) Ignite OSGi: Allow users to create and start Ignite configurations via OSGi Managed Service Factories
[ https://issues.apache.org/jira/browse/IGNITE-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1531: --- Component/s: osgi Summary: Ignite OSGi: Allow users to create and start Ignite configurations via OSGi Managed Service Factories (was: Allow users to create and start Ignite configurations via OSGi Managed Service Factories) > Ignite OSGi: Allow users to create and start Ignite configurations via OSGi > Managed Service Factories > - > > Key: IGNITE-1531 > URL: https://issues.apache.org/jira/browse/IGNITE-1531 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1270) Basic OSGi support for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1270: --- Component/s: osgi > Basic OSGi support for Ignite > - > > Key: IGNITE-1270 > URL: https://issues.apache.org/jira/browse/IGNITE-1270 > Project: Ignite > Issue Type: New Feature > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > Basics for a first iteration: > * Manifest creation for all Java-based modules. > * Apache Karaf features file to facilitate deployment (along with > dependencies). > Future: > * Support peer class-loading. > * Potentially support remote 3rd dependency class-loading for Apache Karaf > (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1528) Support client mode with Ignite OSGi
[ https://issues.apache.org/jira/browse/IGNITE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1528: --- Component/s: osgi > Support client mode with Ignite OSGi > > > Key: IGNITE-1528 > URL: https://issues.apache.org/jira/browse/IGNITE-1528 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1531) Ignite OSGi: Allow users to create and start Ignite configurations via OSGi Managed Service Factories
[ https://issues.apache.org/jira/browse/IGNITE-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1531: --- Issue Type: New Feature (was: Sub-task) Parent: (was: IGNITE-1270) > Ignite OSGi: Allow users to create and start Ignite configurations via OSGi > Managed Service Factories > - > > Key: IGNITE-1531 > URL: https://issues.apache.org/jira/browse/IGNITE-1531 > Project: Ignite > Issue Type: New Feature > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1530) Ignite OSGi: Support Peer Classloading (Zero Deployment)
[ https://issues.apache.org/jira/browse/IGNITE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1530: --- Component/s: osgi > Ignite OSGi: Support Peer Classloading (Zero Deployment) > > > Key: IGNITE-1530 > URL: https://issues.apache.org/jira/browse/IGNITE-1530 > Project: Ignite > Issue Type: New Feature > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles and Karaf features
[ https://issues.apache.org/jira/browse/IGNITE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1527: --- Component/s: osgi > Add OSGi manifest headers to all ignite-core + basic bundles and Karaf > features > --- > > Key: IGNITE-1527 > URL: https://issues.apache.org/jira/browse/IGNITE-1527 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > And make sure they interoperate properly with each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1877) Add ClassLoaderCodec for OSGI support
[ https://issues.apache.org/jira/browse/IGNITE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1877: --- Component/s: osgi > Add ClassLoaderCodec for OSGI support > - > > Key: IGNITE-1877 > URL: https://issues.apache.org/jira/browse/IGNITE-1877 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Dmitriy Setrakyan >Assignee: Raúl Kripalani > Fix For: 1.6 > > > The design is described here: > https://cwiki.apache.org/confluence/display/IGNITE/OSGI+Compatibility -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1877) Make Ignite classloading OSGi-friendly & provide different classloading strategies
[ https://issues.apache.org/jira/browse/IGNITE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1877: --- Fix Version/s: (was: 1.6) 1.5 Summary: Make Ignite classloading OSGi-friendly & provide different classloading strategies (was: Add ClassLoaderCodec for OSGI support) > Make Ignite classloading OSGi-friendly & provide different classloading > strategies > -- > > Key: IGNITE-1877 > URL: https://issues.apache.org/jira/browse/IGNITE-1877 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Dmitriy Setrakyan >Assignee: Raúl Kripalani > Fix For: 1.5 > > > The design is described here: > https://cwiki.apache.org/confluence/display/IGNITE/OSGI+Compatibility -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1270) Basic OSGi support for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1270: --- Description: Basics for a first iteration: * Manifest creation for all Java-based modules. * Apache Karaf features file to facilitate deployment (along with dependencies). * Make Ignite classloading OSGi-friendly and support different strategies. Future: * Support peer class-loading. * Potentially support remote 3rd dependency class-loading for Apache Karaf (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories). was: Basics for a first iteration: * Manifest creation for all Java-based modules. * Apache Karaf features file to facilitate deployment (along with dependencies). Future: * Support peer class-loading. * Potentially support remote 3rd dependency class-loading for Apache Karaf (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories). > Basic OSGi support for Ignite > - > > Key: IGNITE-1270 > URL: https://issues.apache.org/jira/browse/IGNITE-1270 > Project: Ignite > Issue Type: New Feature > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > Basics for a first iteration: > * Manifest creation for all Java-based modules. > * Apache Karaf features file to facilitate deployment (along with > dependencies). > * Make Ignite classloading OSGi-friendly and support different strategies. > Future: > * Support peer class-loading. > * Potentially support remote 3rd dependency class-loading for Apache Karaf > (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1810) Upgrade ignite-aws dependencies (HttpClient and AWS SDK)
[ https://issues.apache.org/jira/browse/IGNITE-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1810: --- Component/s: osgi > Upgrade ignite-aws dependencies (HttpClient and AWS SDK) > > > Key: IGNITE-1810 > URL: https://issues.apache.org/jira/browse/IGNITE-1810 > Project: Ignite > Issue Type: Improvement > Components: aws, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > We need to upgrade the HttpClient and AWS SDK dependencies in ignite-aws. > They are very old: > * AWS SDK 1.3.21.1 => 1.10.29 > * HttpClient 4.2.3 => 4.5.1 > * HttpCore 4.2.3 => 4.4.3 > These upgrades are needed by the OSGi integration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1810) Upgrade ignite-aws dependencies (HttpClient and AWS SDK)
[ https://issues.apache.org/jira/browse/IGNITE-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15025208#comment-15025208 ] Raúl Kripalani commented on IGNITE-1810: Included in ignite-1270 branch. > Upgrade ignite-aws dependencies (HttpClient and AWS SDK) > > > Key: IGNITE-1810 > URL: https://issues.apache.org/jira/browse/IGNITE-1810 > Project: Ignite > Issue Type: Improvement > Components: aws, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > We need to upgrade the HttpClient and AWS SDK dependencies in ignite-aws. > They are very old: > * AWS SDK 1.3.21.1 => 1.10.29 > * HttpClient 4.2.3 => 4.5.1 > * HttpCore 4.2.3 => 4.4.3 > These upgrades are needed by the OSGi integration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1270) Basic OSGi support for Ignite
[
https://issues.apache.org/jira/browse/IGNITE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027062#comment-15027062
]
Raúl Kripalani commented on IGNITE-1270:
Hi Romain,
Thanks for your input! Here's my feedback:
bq. Why you introduce the constrain of having only one ignite instance per jvm?
Unfortunately many Ignite variables/classes are at the static namespace, i.e.
singletons. While this is OK for most non-OSGi containers out there, because
the static classes will be loaded as many times as classloaders, this does not
work in OSGi, because the static classes are only loaded once, and only once,
per container. For example, have a look at {{IgniteUtils#gridClassLoader}}. In
a web container with multiple WARs, each WAR will load its own copy of
IgniteUtils. However, in an OSGi container that's not the case, therefore if we
load multiple grids, the gridClassLoader (and all such variables) will not
differentiate between one grid and another.
*IgniteOsgiUtils*
bq. I think this class should be package protected or in an private package. I
see it more as an internal implementation detail and client should not be
allowed to depends / use.
I didn't make the class private/protected nor static (even though it's a helper
class for now) because in the future it may be necessary from ignite-core (e.g.
serializers) to find out if the current environment is OSGi or not, or get the
appropriate classloader, etc. Keeping it like this allows us to use the
{{IgniteComponentType}} lookup mechanism in the future.
bq. gridCount()
I agree too. Grid in my head is something composed of many nodes. But in
Ignite, the term is used to refer to a single Ignite instance (have a look at
the unit tests).
bq. classloaders()
Good point. I've made {{classloaders()}} protected. When we support multiple
instances, we can add a {{public static ClassLoader getClassLoader(Ignite
ignite)}} method. Until then, exposing an API for this is useless.
bq. Why don't you use the parent child classloader delegation?
Because in OSGi, classloaders are connected in a graph fashion, not in a tree
pattern. The parent classloader is useless here.
bq. Why are you going first to the bundle and then to the class loader. Maybe
you should put the given class loader as a parent and then fallback to the
bundle, no? Because this bundle will import the Ignite package and therefore
its classloader should be able to see some of the ignite classes.
I've followed the model that has worked pretty well in Apache Camel. In pure
OSGi, bundles are always resolved from within the classspace of the current
bundle. This is what the user expects. That's why the bundle receives priority
#1 in my implementation.
bq. Do you plan to support the dynamic addition and removal of bundles? This
dynamicity may impact the nonResolvable and resolved Set. As some classes may
become resolvable and some other not or in a different way [...]
Yes, I agree with you entirely. It is in my roadmap to manage the caches
appropriately as bundles come and go via a {{BundleTracker}}. However, this is
only necessary in a changing environment. For now I don't see it as a blocker,
but it's definitely something to be done in Ignite 1.6 or even 1.5.1.
*IgniteOsgiContextActivator*
bq. Maybe the Abstract key word should be used in the name to make it crystal
clear
Agree, thanks for the note.
bq. You should make the start(BundleContext context) and stop(BundleContext
context) final in order to avoid the hack I mention above.
Hmmm, ok. But in exchange I have introduced callback methods {{preStart}},
{{postStart}}, {{preStop}}, {{postStop}} to give users some flexibility to
introduce custom logic.
*Maven*
bq. In you effort to extract the version maybe we can add a new jira ticket to
also use the dependencyManagement section to avoid to use the version
properties everywhere?
I think it's overkill to add all those dependencies in dependencyManagement,
when most of them are only used in one module. I _could_ see shared
dependencies being moved to dependencyManagement, but I don't like having mixed
criteria and further development overhead. No one is going to remember in the
future to promote an ad-hoc dependency to dependencyManagement if they
introduce a dependency that happens to be used elsewhere... So I rather keep it
as it is. It's already a huge step forward to have dependency versions in
properties, as it facilitates tracking and upgrade management big time.
---
I have pushed my changes to the branch. Have a look again and let me know what
you think.
Thanks for your constructive comments!
Regards,
Raúl.
> Basic OSGi support for Ignite
> -
>
> Key: IGNITE-1270
> URL: https://issues.apache.org/jira
[jira] [Comment Edited] (IGNITE-1270) Basic OSGi support for Ignite
[
https://issues.apache.org/jira/browse/IGNITE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027062#comment-15027062
]
Raúl Kripalani edited comment on IGNITE-1270 at 11/25/15 4:33 PM:
--
Hi Romain,
Thanks for your input! Here's my feedback:
bq. Why you introduce the constrain of having only one ignite instance per jvm?
Unfortunately many Ignite variables/classes are in the static namespace, i.e.
singletons. While this is OK for most non-OSGi containers out there, because
the static classes will be loaded as many times as classloaders, this does not
work in OSGi, because the static classes are only loaded once, and only once,
per container. For example, have a look at {{IgniteUtils#gridClassLoader}}. In
a web container with multiple WARs, each WAR will load its own copy of
IgniteUtils. However, in an OSGi container that's not the case, therefore if we
load multiple grids, the gridClassLoader (and all such variables) will not
differentiate between one grid and another.
*IgniteOsgiUtils*
bq. I think this class should be package protected or in an private package. I
see it more as an internal implementation detail and client should not be
allowed to depends / use.
I didn't make the class private/protected nor static (even though it's a helper
class for now) because in the future it may be necessary from ignite-core (e.g.
serializers) to find out if the current environment is OSGi or not, or get the
appropriate classloader, etc. Keeping it like this allows us to use the
{{IgniteComponentType}} lookup mechanism in the future.
bq. gridCount()
I agree too. Grid in my head is something composed of many nodes. But in
Ignite, the term is used to refer to a single Ignite instance (have a look at
the unit tests).
bq. classloaders()
Good point. I've made {{classloaders()}} protected. When we support multiple
instances, we can add a {{public static ClassLoader getClassLoader(Ignite
ignite)}} method. Until then, exposing an API for this is useless.
bq. Why don't you use the parent child classloader delegation?
Because in OSGi, classloaders are connected in a graph fashion, not in a tree
pattern. The parent classloader is useless here.
bq. Why are you going first to the bundle and then to the class loader. Maybe
you should put the given class loader as a parent and then fallback to the
bundle, no? Because this bundle will import the Ignite package and therefore
its classloader should be able to see some of the ignite classes.
I've followed the model that has worked pretty well in Apache Camel. In pure
OSGi, bundles are always resolved from within the classspace of the current
bundle. This is what the user expects. That's why the bundle receives priority
#1 in my implementation.
bq. Do you plan to support the dynamic addition and removal of bundles? This
dynamicity may impact the nonResolvable and resolved Set. As some classes may
become resolvable and some other not or in a different way [...]
Yes, I agree with you entirely. It is in my roadmap to manage the caches
appropriately as bundles come and go via a {{BundleTracker}}. However, this is
only necessary in a changing environment. For now I don't see it as a blocker,
but it's definitely something to be done in Ignite 1.6 or even 1.5.1.
*IgniteOsgiContextActivator*
bq. Maybe the Abstract key word should be used in the name to make it crystal
clear
Agree, thanks for the note.
bq. You should make the start(BundleContext context) and stop(BundleContext
context) final in order to avoid the hack I mention above.
Hmmm, ok. But in exchange I have introduced callback methods {{preStart}},
{{postStart}}, {{preStop}}, {{postStop}} to give users some flexibility to
introduce custom logic.
*Maven*
bq. In you effort to extract the version maybe we can add a new jira ticket to
also use the dependencyManagement section to avoid to use the version
properties everywhere?
I think it's overkill to add all those dependencies in dependencyManagement,
when most of them are only used in one module. I _could_ see shared
dependencies being moved to dependencyManagement, but I don't like having mixed
criteria and further development overhead. No one is going to remember in the
future to promote an ad-hoc dependency to dependencyManagement if they
introduce a dependency that happens to be used elsewhere... So I rather keep it
as it is. It's already a huge step forward to have dependency versions in
properties, as it facilitates tracking and upgrade management big time.
---
I have pushed my changes to the branch. Have a look again and let me know what
you think.
Thanks for your constructive comments!
Regards,
Raúl.
was (Author: raulvk):
Hi Romain,
Thanks for your input! Here's my feedback:
bq. Why you introduce the constr
[jira] [Updated] (IGNITE-1270) Basic OSGi support for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1270: --- Fix Version/s: (was: 1.5) 1.6 > Basic OSGi support for Ignite > - > > Key: IGNITE-1270 > URL: https://issues.apache.org/jira/browse/IGNITE-1270 > Project: Ignite > Issue Type: New Feature > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.6 > > > Basics for a first iteration: > * Manifest creation for all Java-based modules. > * Apache Karaf features file to facilitate deployment (along with > dependencies). > * Make Ignite classloading OSGi-friendly and support different strategies. > Future: > * Support peer class-loading. > * Potentially support remote 3rd dependency class-loading for Apache Karaf > (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles and Karaf features
[ https://issues.apache.org/jira/browse/IGNITE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1527: --- Fix Version/s: (was: 1.5) 1.6 > Add OSGi manifest headers to all ignite-core + basic bundles and Karaf > features > --- > > Key: IGNITE-1527 > URL: https://issues.apache.org/jira/browse/IGNITE-1527 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.6 > > > And make sure they interoperate properly with each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1528) Support client mode with Ignite OSGi
[ https://issues.apache.org/jira/browse/IGNITE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1528: --- Fix Version/s: (was: 1.5) 1.6 > Support client mode with Ignite OSGi > > > Key: IGNITE-1528 > URL: https://issues.apache.org/jira/browse/IGNITE-1528 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1877) Make Ignite classloading OSGi-friendly & provide different classloading strategies
[ https://issues.apache.org/jira/browse/IGNITE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1877: --- Fix Version/s: (was: 1.5) 1.6 > Make Ignite classloading OSGi-friendly & provide different classloading > strategies > -- > > Key: IGNITE-1877 > URL: https://issues.apache.org/jira/browse/IGNITE-1877 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Dmitriy Setrakyan >Assignee: Raúl Kripalani > Fix For: 1.6 > > > The design is described here: > https://cwiki.apache.org/confluence/display/IGNITE/OSGI+Compatibility -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1529) Support server mode with Ignite OSGi without Peer Classloading
[ https://issues.apache.org/jira/browse/IGNITE-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1529: --- Fix Version/s: 1.6 > Support server mode with Ignite OSGi without Peer Classloading > -- > > Key: IGNITE-1529 > URL: https://issues.apache.org/jira/browse/IGNITE-1529 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.6 > > > Server mode means replication of user classes. Design a way for allow user > bundles to contribute classes to ignite-core, without using > DynamicImport-Package: * -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1810) Upgrade ignite-aws dependencies (HttpClient and AWS SDK)
[ https://issues.apache.org/jira/browse/IGNITE-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1810: --- Fix Version/s: (was: 1.5) 1.6 > Upgrade ignite-aws dependencies (HttpClient and AWS SDK) > > > Key: IGNITE-1810 > URL: https://issues.apache.org/jira/browse/IGNITE-1810 > Project: Ignite > Issue Type: Improvement > Components: aws, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.6 > > > We need to upgrade the HttpClient and AWS SDK dependencies in ignite-aws. > They are very old: > * AWS SDK 1.3.21.1 => 1.10.29 > * HttpClient 4.2.3 => 4.5.1 > * HttpCore 4.2.3 => 4.4.3 > These upgrades are needed by the OSGi integration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds
[
https://issues.apache.org/jira/browse/IGNITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani updated IGNITE-530:
--
Fix Version/s: 1.5
> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Lalit Kumar Jha
> Fix For: 1.5
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data 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] [Assigned] (IGNITE-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds
[
https://issues.apache.org/jira/browse/IGNITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani reassigned IGNITE-530:
-
Assignee: Anton Vinogradov (was: Lalit Kumar Jha)
Anton,
Could you please fix {{IgniteTwitterStreamerTestSuite}}, as it does not adhere
to test suite conventions in Ignite?
Raúl.
> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data 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-530) Implement IgniteTwitterStreamer to stream data from Twitter feeds
[
https://issues.apache.org/jira/browse/IGNITE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15029989#comment-15029989
]
Raúl Kripalani commented on IGNITE-530:
---
Yes.
> Implement IgniteTwitterStreamer to stream data from Twitter feeds
> -
>
> Key: IGNITE-530
> URL: https://issues.apache.org/jira/browse/IGNITE-530
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Anton Vinogradov
> Fix For: 1.5
>
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> We should create {{IgniteTwitterStreamer}} which will consume messages from
> Twitter and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Twitter data 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] [Updated] (IGNITE-1270) Basic OSGi support for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1270: --- Fix Version/s: (was: 1.6) 1.5 > Basic OSGi support for Ignite > - > > Key: IGNITE-1270 > URL: https://issues.apache.org/jira/browse/IGNITE-1270 > Project: Ignite > Issue Type: New Feature > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > Attachments: osgi-tests.log > > > Basics for a first iteration: > * Manifest creation for all Java-based modules. > * Apache Karaf features file to facilitate deployment (along with > dependencies). > * Make Ignite classloading OSGi-friendly and support different strategies. > Future: > * Support peer class-loading. > * Potentially support remote 3rd dependency class-loading for Apache Karaf > (via Pax Mvn URL and Aether, one can fetch a bundle from Maven repositories). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1529) Support server mode with Ignite OSGi without Peer Classloading
[ https://issues.apache.org/jira/browse/IGNITE-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1529: --- Fix Version/s: (was: 1.6) 1.5 > Support server mode with Ignite OSGi without Peer Classloading > -- > > Key: IGNITE-1529 > URL: https://issues.apache.org/jira/browse/IGNITE-1529 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > Server mode means replication of user classes. Design a way for allow user > bundles to contribute classes to ignite-core, without using > DynamicImport-Package: * -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1528) Support client mode with Ignite OSGi
[ https://issues.apache.org/jira/browse/IGNITE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani resolved IGNITE-1528. Resolution: Fixed > Support client mode with Ignite OSGi > > > Key: IGNITE-1528 > URL: https://issues.apache.org/jira/browse/IGNITE-1528 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1877) Make Ignite classloading OSGi-friendly & provide different classloading strategies
[ https://issues.apache.org/jira/browse/IGNITE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1877: --- Fix Version/s: (was: 1.6) 1.5 > Make Ignite classloading OSGi-friendly & provide different classloading > strategies > -- > > Key: IGNITE-1877 > URL: https://issues.apache.org/jira/browse/IGNITE-1877 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Dmitriy Setrakyan >Assignee: Raúl Kripalani > Fix For: 1.5 > > > The design is described here: > https://cwiki.apache.org/confluence/display/IGNITE/OSGI+Compatibility -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1877) Make Ignite classloading OSGi-friendly & provide different classloading strategies
[ https://issues.apache.org/jira/browse/IGNITE-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani resolved IGNITE-1877. Resolution: Fixed > Make Ignite classloading OSGi-friendly & provide different classloading > strategies > -- > > Key: IGNITE-1877 > URL: https://issues.apache.org/jira/browse/IGNITE-1877 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Dmitriy Setrakyan >Assignee: Raúl Kripalani > Fix For: 1.5 > > > The design is described here: > https://cwiki.apache.org/confluence/display/IGNITE/OSGI+Compatibility -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles and Karaf features
[ https://issues.apache.org/jira/browse/IGNITE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1527: --- Fix Version/s: (was: 1.6) 1.5 > Add OSGi manifest headers to all ignite-core + basic bundles and Karaf > features > --- > > Key: IGNITE-1527 > URL: https://issues.apache.org/jira/browse/IGNITE-1527 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > And make sure they interoperate properly with each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1810) Upgrade ignite-aws dependencies (HttpClient and AWS SDK)
[ https://issues.apache.org/jira/browse/IGNITE-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1810: --- Fix Version/s: (was: 1.6) 1.5 > Upgrade ignite-aws dependencies (HttpClient and AWS SDK) > > > Key: IGNITE-1810 > URL: https://issues.apache.org/jira/browse/IGNITE-1810 > Project: Ignite > Issue Type: Improvement > Components: aws, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > We need to upgrade the HttpClient and AWS SDK dependencies in ignite-aws. > They are very old: > * AWS SDK 1.3.21.1 => 1.10.29 > * HttpClient 4.2.3 => 4.5.1 > * HttpCore 4.2.3 => 4.4.3 > These upgrades are needed by the OSGi integration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1528) Support client mode with Ignite OSGi
[ https://issues.apache.org/jira/browse/IGNITE-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani updated IGNITE-1528: --- Fix Version/s: (was: 1.6) 1.5 > Support client mode with Ignite OSGi > > > Key: IGNITE-1528 > URL: https://issues.apache.org/jira/browse/IGNITE-1528 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1527) Add OSGi manifest headers to all ignite-core + basic bundles and Karaf features
[ https://issues.apache.org/jira/browse/IGNITE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani resolved IGNITE-1527. Resolution: Fixed > Add OSGi manifest headers to all ignite-core + basic bundles and Karaf > features > --- > > Key: IGNITE-1527 > URL: https://issues.apache.org/jira/browse/IGNITE-1527 > Project: Ignite > Issue Type: Sub-task > Components: general, osgi >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > And make sure they interoperate properly with each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1529) Support server mode with Ignite OSGi without Peer Classloading
[ https://issues.apache.org/jira/browse/IGNITE-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani resolved IGNITE-1529. Resolution: Fixed > Support server mode with Ignite OSGi without Peer Classloading > -- > > Key: IGNITE-1529 > URL: https://issues.apache.org/jira/browse/IGNITE-1529 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Raúl Kripalani >Assignee: Raúl Kripalani > Fix For: 1.5 > > > Server mode means replication of user classes. Design a way for allow user > bundles to contribute classes to ignite-core, without using > DynamicImport-Package: * -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2172) Uneven API between IgniteMessaging#stopRemoteListen and #stopLocalListen
Raúl Kripalani created IGNITE-2172:
--
Summary: Uneven API between IgniteMessaging#stopRemoteListen and
#stopLocalListen
Key: IGNITE-2172
URL: https://issues.apache.org/jira/browse/IGNITE-2172
Project: Ignite
Issue Type: Improvement
Components: messaging
Affects Versions: 1.5
Reporter: Raúl Kripalani
Compare:
{code}
UUID remoteListen(@Nullable Object topic, IgniteBiPredicate p)
{code}
vs.
{code}
void stopLocalListen(@Nullable Object topic, IgniteBiPredicate p)
{code}
It would be nice to identify local listeners with an UUID too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060221#comment-15060221
]
Raúl Kripalani commented on IGNITE-2116:
Hi,
This module generates no binaries. The module is of type pom. It just contains
resources which are attached to the build (the features descriptor).
It would be nice to include the latter inside the fabric package.
Regards,
Raúl.
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Raúl Kripalani
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani reassigned IGNITE-2116:
--
Assignee: Sergey Kozlov (was: Raúl Kripalani)
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Sergey Kozlov
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1192) Provide integration with Spring Data
[ https://issues.apache.org/jira/browse/IGNITE-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060750#comment-15060750 ] Jörn Franke commented on IGNITE-1192: - I will write later a little bit more, but I assume it is about integrating spring-data with Ignite Datagrid. IGFS and Hadoop MR Jobs on Ignite can be already accessed via spring-data-hadoop > Provide integration with Spring Data > > > Key: IGNITE-1192 > URL: https://issues.apache.org/jira/browse/IGNITE-1192 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.1.4 >Reporter: Valentin Kulichenko >Priority: Minor > Labels: Newbie > Fix For: 1.6 > > > Spring Data docs: > * http://docs.spring.io/spring-data/data-commons/docs/current/reference/html/ > * http://docs.spring.io/spring-data/data-commons/docs/current/api/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062044#comment-15062044
]
Raúl Kripalani commented on IGNITE-2116:
Hey,
You should add the generated features.xml (in the target directory, after the
build has run) to this folder.
Regards,
Raúl.
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Raúl Kripalani
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raúl Kripalani reassigned IGNITE-2116:
--
Assignee: Anton Vinogradov (was: Raúl Kripalani)
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2116) ignite-osgi-karaf has only readme and license files
[
https://issues.apache.org/jira/browse/IGNITE-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068126#comment-15068126
]
Raúl Kripalani commented on IGNITE-2116:
Hi [~avinogradov],
You don't need to be familiar with OSGi.
This module simply contains an XML file with placeholders that are replaced by
Maven Resource Filtering.
You just need to copy the file: {{target/classes/features.xml}} into the fabric
assembly module.
Regards,
Raúl.
> ignite-osgi-karaf has only readme and license files
> ---
>
> Key: IGNITE-2116
> URL: https://issues.apache.org/jira/browse/IGNITE-2116
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.5
>Reporter: Sergey Kozlov
>Assignee: Anton Vinogradov
>Priority: Critical
> Fix For: 1.5
>
>
> {noformat}
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:34 licenses
> 08.12.2015 12:34 735 README.txt
> ...
> C:\Work\apache-ignite-fabric-1.5.0-b2-bin\libs\optional\ignite-osgi-karaf>dir
> licenses
> ...
> 08.12.2015 12:34 .
> 08.12.2015 12:34 ..
> 08.12.2015 12:3411 358 apache-2.0.txt
> 08.12.2015 12:34 289 ignite-osgi-karaf-licenses.txt
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2718) modules/zookeeper/target/libs directory does not have all dependencies
[
https://issues.apache.org/jira/browse/IGNITE-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177701#comment-15177701
]
Raúl Kripalani commented on IGNITE-2718:
Sorry for the delay. [~roman_s], yes, that's absolutely fine. In fact, it's not
a good practice to rely on transitive dependencies of 3rd parties, better to
declare them explicitly.
Cheers!
> modules/zookeeper/target/libs directory does not have all dependencies
> --
>
> Key: IGNITE-2718
> URL: https://issues.apache.org/jira/browse/IGNITE-2718
> Project: Ignite
> Issue Type: Bug
> Components: build, ignite-zookeeper
>Reporter: Dustin Chesterman
>Assignee: Roman Shtykh
>Priority: Critical
> Labels: community
> Fix For: 1.6
>
>
> If you specify the zookeeper ip finder in the example cache config there are
> a host of classnotfound exceptions. I believe these need to be populated
> into the build target lib dir.
> {code}
>
>
>
>
>
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.TcpDiscoveryZookeeperIpFinder">
> value="false" />
>
>
> value="192.168.200.11:2181" />
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (IGNITE-813) Apache Flink Integration -- data streaming connector
[ https://issues.apache.org/jira/browse/IGNITE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Kripalani reopened IGNITE-813: --- Hi [~samaitra], Sorry to reopen the ticket, but unfortunately we don't seem to have any docs in readme.io. I know this is the most boring part, but I think you're the right person to write them, so the community would appreciate your help! Could you please contribute a little markdown file with the Apache License at the top (as an attachment to this ticket) so we can copy and paste it into our docs at readme.io? Have a look at the MQTT streamer as an example: https://apacheignite.readme.io/docs/mqtt-streamer. Cheers! Raúl. > Apache Flink Integration -- data streaming connector > > > Key: IGNITE-813 > URL: https://issues.apache.org/jira/browse/IGNITE-813 > Project: Ignite > Issue Type: New Feature > Components: streaming >Reporter: Suminda Dharmasena >Assignee: Saikat Maitra > Fix For: 1.6 > > > Sink connector -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-19489) Cancel updateDistributedConfigurationActionFuture if the configuration is applied
[ https://issues.apache.org/jira/browse/IGNITE-19489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Sizov updated IGNITE-19489: --- Epic Link: IGNITE-19280 > Cancel updateDistributedConfigurationActionFuture if the configuration is > applied > - > > Key: IGNITE-19489 > URL: https://issues.apache.org/jira/browse/IGNITE-19489 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Gagarkin >Priority: Major > Labels: ignite-3 > > org.apache.ignite.internal.cluster.management.ClusterManagementGroupManager#updateDistributedConfigurationActionFuture > should be canceled on all nodes, when the leader applies the configuration -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19294) Combine configuration root for several modules
[
https://issues.apache.org/jira/browse/IGNITE-19294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov updated IGNITE-19294:
---
Summary: Combine configuration root for several modules (was: Union
configuration root for several modules)
> Combine configuration root for several modules
> --
>
> Key: IGNITE-19294
> URL: https://issues.apache.org/jira/browse/IGNITE-19294
> Project: Ignite
> Issue Type: New Feature
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> Сurrently, the configuration root can only be modified and extended in the
> module where the configuration root is defined. Let's describe the situation.
> Module *A* -> configuration root *Root1*
> Module *B* depends on module {*}A{*}. In some cases, module *B* wants to
> extend the *Root1* configuration with additional staff, but this is currently
> not possible. This limitation looks artificial and there are cases when this
> extension is necessary and in the current architecture we have to create a
> separate root for each module, which, from the point of view of configuration
> semantics, may look quite strange for the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19294) Support merged configuration roots for multiple modules
[
https://issues.apache.org/jira/browse/IGNITE-19294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov updated IGNITE-19294:
---
Summary: Support merged configuration roots for multiple modules (was:
Combine configuration root for several modules)
> Support merged configuration roots for multiple modules
> ---
>
> Key: IGNITE-19294
> URL: https://issues.apache.org/jira/browse/IGNITE-19294
> Project: Ignite
> Issue Type: New Feature
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> Сurrently, the configuration root can only be modified and extended in the
> module where the configuration root is defined. Let's describe the situation.
> Module *A* -> configuration root *Root1*
> Module *B* depends on module {*}A{*}. In some cases, module *B* wants to
> extend the *Root1* configuration with additional staff, but this is currently
> not possible. This limitation looks artificial and there are cases when this
> extension is necessary and in the current architecture we have to create a
> separate root for each module, which, from the point of view of configuration
> semantics, may look quite strange for the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19291) Generate default node configuration file on compile-time
[ https://issues.apache.org/jira/browse/IGNITE-19291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Sizov reassigned IGNITE-19291: -- Assignee: Kirill Sizov > Generate default node configuration file on compile-time > > > Key: IGNITE-19291 > URL: https://issues.apache.org/jira/browse/IGNITE-19291 > Project: Ignite > Issue Type: New Feature >Reporter: Mikhail Pochatkin >Assignee: Kirill Sizov >Priority: Major > Labels: ignite-3 > > Currently all configration defaults exists only in schema description (in > code). This is not clear for users which configration values is used. It is > proposed to generate HOCON configuration file with all defaults on compile > time. This file should be passed to all distibutions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-19291) Generate default node configuration file at compile-time
[ https://issues.apache.org/jira/browse/IGNITE-19291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Sizov updated IGNITE-19291: --- Summary: Generate default node configuration file at compile-time (was: Generate default node configuration file on compile-time) > Generate default node configuration file at compile-time > > > Key: IGNITE-19291 > URL: https://issues.apache.org/jira/browse/IGNITE-19291 > Project: Ignite > Issue Type: New Feature >Reporter: Mikhail Pochatkin >Assignee: Kirill Sizov >Priority: Major > Labels: ignite-3 > > Currently all configration defaults exists only in schema description (in > code). This is not clear for users which configration values is used. It is > proposed to generate HOCON configuration file with all defaults on compile > time. This file should be passed to all distibutions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19294) Support merged configuration roots for multiple modules
[
https://issues.apache.org/jira/browse/IGNITE-19294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov reassigned IGNITE-19294:
--
Assignee: Kirill Sizov
> Support merged configuration roots for multiple modules
> ---
>
> Key: IGNITE-19294
> URL: https://issues.apache.org/jira/browse/IGNITE-19294
> Project: Ignite
> Issue Type: New Feature
>Reporter: Mikhail Pochatkin
>Assignee: Kirill Sizov
>Priority: Major
> Labels: ignite-3
>
> Сurrently, the configuration root can only be modified and extended in the
> module where the configuration root is defined. Let's describe the situation.
> Module *A* -> configuration root *Root1*
> Module *B* depends on module {*}A{*}. In some cases, module *B* wants to
> extend the *Root1* configuration with additional staff, but this is currently
> not possible. This limitation looks artificial and there are cases when this
> extension is necessary and in the current architecture we have to create a
> separate root for each module, which, from the point of view of configuration
> semantics, may look quite strange for the user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-19922) Gradle checkstyle tasks are greedy
[
https://issues.apache.org/jira/browse/IGNITE-19922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749935#comment-17749935
]
Kirill Sizov commented on IGNITE-19922:
Some low-hanging fruits on configuring Gradle to reduce the pressure on the OS.
The reason why the daemons don't go away is the way Gradle was designed:
??These worker daemon processes will persist across builds and can be reused
during subsequent builds. If system resources get low, however, Gradle will
stop any unused worker daemons.??
[https://docs.gradle.org/current/userguide/worker_api.html#creating_a_worker_daemon]
Starting the build with {{--no-daemon}} parameter should help.
There is a way to limit the number of parallel workers to any desired number:
[https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_configuration_properties]
Either by passing an extra command line argument {{--max-workers}}
Or by setting {{org.gradle.workers.max}} property in
{{~/.gradle/gradle.properties}}
> Gradle checkstyle tasks are greedy
> --
>
> Key: IGNITE-19922
> URL: https://issues.apache.org/jira/browse/IGNITE-19922
> Project: Ignite
> Issue Type: New Feature
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
> Attachments: image-2023-07-06-11-18-40-515.png, screenshot-1.png
>
>
> This is memory consumption during {{gradlew checkstyleMain}} execution -
> goes from ~10 GB to 30. All CPU cores are also at 100%. This causes chrome
> tabs to unload and overall stress on the system.
> Also, RAM usage does not go down after this command unless I kill/stop Gradle
> daemons
> !image-2023-07-06-11-18-40-515.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19922) Gradle checkstyle tasks are greedy
[
https://issues.apache.org/jira/browse/IGNITE-19922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov reassigned IGNITE-19922:
--
Assignee: Kirill Sizov
> Gradle checkstyle tasks are greedy
> --
>
> Key: IGNITE-19922
> URL: https://issues.apache.org/jira/browse/IGNITE-19922
> Project: Ignite
> Issue Type: New Feature
>Reporter: Mikhail Pochatkin
>Assignee: Kirill Sizov
>Priority: Major
> Labels: ignite-3
> Attachments: image-2023-07-06-11-18-40-515.png, screenshot-1.png
>
>
> This is memory consumption during {{gradlew checkstyleMain}} execution -
> goes from ~10 GB to 30. All CPU cores are also at 100%. This causes chrome
> tabs to unload and overall stress on the system.
> Also, RAM usage does not go down after this command unless I kill/stop Gradle
> daemons
> !image-2023-07-06-11-18-40-515.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (IGNITE-19922) Gradle checkstyle tasks are greedy
[
https://issues.apache.org/jira/browse/IGNITE-19922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov resolved IGNITE-19922.
Resolution: Won't Fix
Command line parameter helped.
Closing this Jira.
> Gradle checkstyle tasks are greedy
> --
>
> Key: IGNITE-19922
> URL: https://issues.apache.org/jira/browse/IGNITE-19922
> Project: Ignite
> Issue Type: New Feature
>Reporter: Mikhail Pochatkin
>Assignee: Kirill Sizov
>Priority: Major
> Labels: ignite-3
> Attachments: image-2023-07-06-11-18-40-515.png, screenshot-1.png
>
>
> This is memory consumption during {{gradlew checkstyleMain}} execution -
> goes from ~10 GB to 30. All CPU cores are also at 100%. This causes chrome
> tabs to unload and overall stress on the system.
> Also, RAM usage does not go down after this command unless I kill/stop Gradle
> daemons
> !image-2023-07-06-11-18-40-515.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-19792) Support @Immutable logic for distributed configuration
[
https://issues.apache.org/jira/browse/IGNITE-19792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Sizov reassigned IGNITE-19792:
--
Assignee: Kirill Sizov
> Support @Immutable logic for distributed configuration
> --
>
> Key: IGNITE-19792
> URL: https://issues.apache.org/jira/browse/IGNITE-19792
> Project: Ignite
> Issue Type: Improvement
>Reporter: Roman Puchkovskiy
>Assignee: Kirill Sizov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> For distributed properties, the following scenario makes sense:
> # Property value might be set on cluster init
> # If it is provided, it overrides the default; otherwise, the default (set
> in the {{@Value}} annotation) is used
> # Any attempt to modify the property value using a changer is rejected by a
> validator
> {{@Immutable}} annotation is designed to trigger such behavior.
> Now, the observed behavior is different: if a property is annotated as
> {{{}@Immutable{}}}, then, if a value is supplied during cluster
> initialization, the value is silently ignored, so it is impossible to
> configure such property to anything different from the default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-19911) Initial cluster configuration should be validated against the default configuration
[ https://issues.apache.org/jira/browse/IGNITE-19911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Sizov updated IGNITE-19911: --- Epic Link: IGNITE-19280 > Initial cluster configuration should be validated against the default > configuration > --- > > Key: IGNITE-19911 > URL: https://issues.apache.org/jira/browse/IGNITE-19911 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Gagarkin >Priority: Critical > Labels: ignite-3 > > Users can set a custom cluster configuration on init. That configuration is > validated against an empty configuration. It's not correct because the > cluster is initialized with the default configuration first, and then a > custom configuration is applied. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-19911) Initial cluster configuration should be validated against the default configuration
[ https://issues.apache.org/jira/browse/IGNITE-19911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Sizov reassigned IGNITE-19911: -- Assignee: Kirill Sizov > Initial cluster configuration should be validated against the default > configuration > --- > > Key: IGNITE-19911 > URL: https://issues.apache.org/jira/browse/IGNITE-19911 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Gagarkin >Assignee: Kirill Sizov >Priority: Critical > Labels: ignite-3 > > Users can set a custom cluster configuration on init. That configuration is > validated against an empty configuration. It's not correct because the > cluster is initialized with the default configuration first, and then a > custom configuration is applied. -- This message was sent by Atlassian Jira (v8.20.10#820010)
