[jira] [Updated] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ihor Parashynets updated IGNITE-6284: - Attachment: image-2018-04-23-21-54-06-341.png > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > Attachments: image-2018-04-23-21-54-06-341.png > > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[
https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448778#comment-16448778
]
Ihor Parashynets commented on IGNITE-6284:
--
hi [~dpavlov]
I guess the ticket was created under user list discussion here -
[http://apache-ignite-users.70518.x6.nabble.com/Task-management-MapReduce-amp-ForkJoin-performance-penalty-td16542.html]
at {{Sep 06, 2017; 5:51pm}}
> Add IgniteCompute.withTaskNoResultCache() which should have similar effect as
> @ComputeTaskNoResultCache
> ---
>
> Key: IGNITE-6284
> URL: https://issues.apache.org/jira/browse/IGNITE-6284
> Project: Ignite
> Issue Type: Improvement
> Components: compute
>Reporter: Yakov Zhdanov
>Assignee: Mikhail Lipkovich
>Priority: Major
> Labels: newbie, usability
> Attachments: image-2018-04-23-21-54-06-341.png
>
>
> New method should save threadlocal context as other IgniteCompute.with...()
> methods do and have similar effect as ComputeTaskNoResultCache annotation
> attached to a class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ihor Parashynets updated IGNITE-6284: - Attachment: (was: image-2018-04-23-21-54-06-341.png) > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493649#comment-16493649 ] Ihor Parashynets commented on IGNITE-6284: -- hi guys Is it possible to predict in which version this ticket might come? Is there somebody going to review it? Thanks you in advance > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6284) Add IgniteCompute.withTaskNoResultCache() which should have similar effect as @ComputeTaskNoResultCache
[ https://issues.apache.org/jira/browse/IGNITE-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493677#comment-16493677 ] Ihor Parashynets commented on IGNITE-6284: -- hi [~dpavlov], [~EdShangGG] Thank you both for the quick response. I'm not sure if I'll be able reasonably evaluate latest changes here (such as didn't study AI internally as a developer) but anyway very appreciated! In case it's stacked for longer time I might give it a try from my side :) cheers, Ihor P. > Add IgniteCompute.withTaskNoResultCache() which should have similar effect as > @ComputeTaskNoResultCache > --- > > Key: IGNITE-6284 > URL: https://issues.apache.org/jira/browse/IGNITE-6284 > Project: Ignite > Issue Type: Improvement > Components: compute >Reporter: Yakov Zhdanov >Assignee: Mikhail Lipkovich >Priority: Major > Labels: newbie, usability > > New method should save threadlocal context as other IgniteCompute.with...() > methods do and have similar effect as ComputeTaskNoResultCache annotation > attached to a class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5037) Fix broken @AffinityKeyMapped annotation for compute jobs.
[ https://issues.apache.org/jira/browse/IGNITE-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559647#comment-16559647 ] Ihor Parashynets commented on IGNITE-5037: -- hi [~ezhuravl] If I may ask - is there a chance that you did some progress for this ticket? Many thanks in advance! > Fix broken @AffinityKeyMapped annotation for compute jobs. > -- > > Key: IGNITE-5037 > URL: https://issues.apache.org/jira/browse/IGNITE-5037 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.7 >Reporter: Alexei Scherbakov >Assignee: Evgenii Zhuravlev >Priority: Major > Labels: newbie > > See related discussion on dev list entitled Proper collocation of > computations and data > (http://apache-ignite-developers.2346864.n4.nabble.com/Proper-collocation-of-computations-and-data-td16945.html). > We must repair data affinity routing for compute jobs. It should work same as > for affinityCall/Run with partition. > Currently, ComputeTask map method returns Map ClusterNode>, > but we have to provide some API allows to map ComputeJobs to partitions or > keys. > This can be done using AffinityKeyMapped annotation or any other way. > Since that's a publiс API any fixes should be discussed on dev list prior to > implementation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5037) Fix broken @AffinityKeyMapped annotation for compute jobs.
[ https://issues.apache.org/jira/browse/IGNITE-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222322#comment-16222322 ] Ihor Parashynets commented on IGNITE-5037: -- hello [~dreamx] May I ask you a question if you have some plans about time-line of finishing this ticket? This is one of crucial feature, which is required by our customer under switch from Hazelcast to Apache Ignite. Many thanks in advance! > Fix broken @AffinityKeyMapped annotation for compute jobs. > -- > > Key: IGNITE-5037 > URL: https://issues.apache.org/jira/browse/IGNITE-5037 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.7 >Reporter: Alexei Scherbakov >Assignee: Maksim Kozlov > Labels: newbie > > See related discussion on dev list entitled Proper collocation of > computations and data > (http://apache-ignite-developers.2346864.n4.nabble.com/Proper-collocation-of-computations-and-data-td16945.html). > We must repair data affinity routing for compute jobs. It should work same as > for affinityCall/Run with partition. > Currently, ComputeTask map method returns Map ClusterNode>, > but we have to provide some API allows to map ComputeJobs to partitions or > keys. > This can be done using AffinityKeyMapped annotation or any other way. > Since that's a publiс API any fixes should be discussed on dev list prior to > implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5037) Fix broken @AffinityKeyMapped annotation for compute jobs.
[
https://issues.apache.org/jira/browse/IGNITE-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224012#comment-16224012
]
Ihor Parashynets commented on IGNITE-5037:
--
[~ascherbakov]
Thank you for your response.
I actually asked some questions (including description of evaluation for my
use-case) on user list
[here|http://apache-ignite-users.70518.x6.nabble.com/Task-management-MapReduce-amp-ForkJoin-performance-penalty-td16542.html].
I got the solution, which allows to execute jobs in collocated manner... but
what I'd like to have (if I understood properly description of this ticket) is
to have this feature with help of Ignite's {{MapReduce API}} framework.
Meaning, I'd like to create a {{ComputeTask}} ({{ComputeTaskAdapter}} or
{{ComputeTaskSplitAdapter}}), which would spawn {{ComputeJob}} with affinity
key (annotation or injection) and execute them on node with co-located data.
Otherwise I'd have to create my own "structure", where I'd have to move my
"jobs" to callable/runnable objects and then run them as
affinityRunAsync/affinityCallAsync.
I thought if this ticket would be implemented I'd get really nice way to
achieve this almost out-of-the-box.
> Fix broken @AffinityKeyMapped annotation for compute jobs.
> --
>
> Key: IGNITE-5037
> URL: https://issues.apache.org/jira/browse/IGNITE-5037
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.7
>Reporter: Alexei Scherbakov
>Assignee: Maksim Kozlov
> Labels: newbie
>
> See related discussion on dev list entitled Proper collocation of
> computations and data
> (http://apache-ignite-developers.2346864.n4.nabble.com/Proper-collocation-of-computations-and-data-td16945.html).
> We must repair data affinity routing for compute jobs. It should work same as
> for affinityCall/Run with partition.
> Currently, ComputeTask map method returns Map ClusterNode>,
> but we have to provide some API allows to map ComputeJobs to partitions or
> keys.
> This can be done using AffinityKeyMapped annotation or any other way.
> Since that's a publiс API any fixes should be discussed on dev list prior to
> implementation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5037) Fix broken @AffinityKeyMapped annotation for compute jobs.
[
https://issues.apache.org/jira/browse/IGNITE-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224072#comment-16224072
]
Ihor Parashynets commented on IGNITE-5037:
--
[~dethmix]
correct. I just was thinking if the ticket is in progress state (and previously
had even fix version {{2.3}}) then it would be worth to wait a little bit to
get this feature.
It would be very handy to have such {{API}} indeed...
> Fix broken @AffinityKeyMapped annotation for compute jobs.
> --
>
> Key: IGNITE-5037
> URL: https://issues.apache.org/jira/browse/IGNITE-5037
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 1.7
>Reporter: Alexei Scherbakov
>Assignee: Maksim Kozlov
> Labels: newbie
>
> See related discussion on dev list entitled Proper collocation of
> computations and data
> (http://apache-ignite-developers.2346864.n4.nabble.com/Proper-collocation-of-computations-and-data-td16945.html).
> We must repair data affinity routing for compute jobs. It should work same as
> for affinityCall/Run with partition.
> Currently, ComputeTask map method returns Map ClusterNode>,
> but we have to provide some API allows to map ComputeJobs to partitions or
> keys.
> This can be done using AffinityKeyMapped annotation or any other way.
> Since that's a publiс API any fixes should be discussed on dev list prior to
> implementation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-5037) Fix broken @AffinityKeyMapped annotation for compute jobs.
[ https://issues.apache.org/jira/browse/IGNITE-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322421#comment-16322421 ] Ihor Parashynets commented on IGNITE-5037: -- It would really-really good to see some progress here. [~ezhuravl] - I guess there is a high probability that this ticket could be handed over to you, such as [~dreamx] didn't answer to "the same" question since 27/Oct/2017 > Fix broken @AffinityKeyMapped annotation for compute jobs. > -- > > Key: IGNITE-5037 > URL: https://issues.apache.org/jira/browse/IGNITE-5037 > Project: Ignite > Issue Type: Improvement >Affects Versions: 1.7 >Reporter: Alexei Scherbakov >Assignee: Maksim Kozlov > Labels: newbie > > See related discussion on dev list entitled Proper collocation of > computations and data > (http://apache-ignite-developers.2346864.n4.nabble.com/Proper-collocation-of-computations-and-data-td16945.html). > We must repair data affinity routing for compute jobs. It should work same as > for affinityCall/Run with partition. > Currently, ComputeTask map method returns Map ClusterNode>, > but we have to provide some API allows to map ComputeJobs to partitions or > keys. > This can be done using AffinityKeyMapped annotation or any other way. > Since that's a publiс API any fixes should be discussed on dev list prior to > implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-4012) Compile issues with v1.7.0/1.8.0 - missing dependency & H2 issue
[
https://issues.apache.org/jira/browse/IGNITE-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930118#comment-15930118
]
Ihor Parashynets commented on IGNITE-4012:
--
hi all
The same story for newly released 1.9.0 version...
> Compile issues with v1.7.0/1.8.0 - missing dependency & H2 issue
>
>
> Key: IGNITE-4012
> URL: https://issues.apache.org/jira/browse/IGNITE-4012
> Project: Ignite
> Issue Type: Bug
> Components: build
>Affects Versions: 1.7, 1.8
>Reporter: Steve White
>
> Hi, I'd just like to mention a couple of build issues - not sure if you're
> aware.
> If I build Apache Ignite tags/1.7.0 (1.7.0-SNAPSHOT) & master
> (1.8.0-SNAPSHOT) I get:
> {code}
> Missing dependencies:
> [ERROR] Failed to execute goal on project ignite-core: Could not resolve
> dependencies for project org.apache.ignite:ignite-core:jar:1.7.0-SNAPSHOT:
> The following artifacts could not be resolved:
> org.apache.ignite.binary:test1:jar:1.1,
> org.apache.ignite.binary:test2:jar:1.1:
> {code}
> If I comment the ignite-core:test1,test2 dependencies out I get a bunch of
> compile time errors in the indexing module referencing h2, just to mention a
> couple:
> {code}
> GridMergeIndex.java:[298,16] method getCostRangeIndex in class
> org.h2.index.BaseIndex cannot be applied to given types;
> [ERROR] required:
> int[],long,org.h2.table.TableFilter[],int,org.h2.result.SortOrder,boolean,java.util.HashSet
> [ERROR] found:
> int[],long,org.h2.table.TableFilter[],int,org.h2.result.SortOrder,boolean
> [ERROR] reason: actual and formal argument lists differ in length
> GridH2TreeIndex.java:[49,8]
> org.apache.ignite.internal.processors.query.h2.opt.GridH2TreeIndex is not
> abstract and does
> not override abstract method
> getCost(org.h2.engine.Session,int[],org.h2.table.TableFilter[],int,org.h2.result.SortOrder,java.util.HashSet)
> in org.h2.index.Index
> {code}
> Restricting building a subset of modules works, e.g:
> {code}
> mvn clean install -DskipTests -Dmaven.javadoc.skip=true -pl
> modules/apache-license-gen,modules/tools,modules/core,modules/osgi,modules/spring,modules/slf4j
> {code}
> But I really need indexing. My next step is to be drop the pom to an earlier
> version of H2 to try get it built. My reasons for building from source are to
> include a number of additional OSGi package imports (TBC).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (IGNITE-1264) Resource SPI
[ https://issues.apache.org/jira/browse/IGNITE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006193#comment-16006193 ] Ihor Parashynets commented on IGNITE-1264: -- hi all is there a plan to move on this topic? Thanks... > Resource SPI > > > Key: IGNITE-1264 > URL: https://issues.apache.org/jira/browse/IGNITE-1264 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Andrey Kornev > > As a user I'd like to be able to customize how resource injection is done by > Ignite: for example, I'd like to be able to process any custom annotations on > my application's class after its deserialization on a remote node. > Ideally, Ignite should expose an SPI that would be delegated to at specific > points of the dependency injection logic (as currently implemented in the > GridResourceProcessor class). > Once implemented, this feature would allow to make the injector support > pluggable: Spring, Guice, Dagger, whatever... Ultimately it'd be great to > replace all injection-related Ignite annotations by the standard javax.inject > API. > For references, here's the nabble thread: > http://apache-ignite-developers.2346864.n4.nabble.com/Resource-SPI-proposal-td2318.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
