rpuch commented on a change in pull request #715: URL: https://github.com/apache/ignite-3/pull/715#discussion_r824758729
########## File path: modules/compute-api/src/main/java/org/apache/ignite/compute/ComputeJob.java ########## @@ -0,0 +1,34 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contributor license agreements. See the NOTICE file distributed with + * this work for additional information regarding copyright ownership. + * The ASF licenses this file to You under the Apache License, Version 2.0 + * (the "License"); you may not use this file except in compliance with + * the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ + +package org.apache.ignite.compute; + +/** + * A Compute job that may be executed on an Ignite node (or a few nodes, or on the whole cluster). + * + * @param <R> job result type + */ +public interface ComputeJob<R> { Review comment: It's an interesting question. Here https://issues.apache.org/jira/browse/IGNITE-16613 the `Serializable` is omitted. The current `IgniteCompute` API (namely, the fact that it accepts job class, not job instance) makes me think that we do not need to pass job instances from node to node, instead it seems that each node can instantiate its own instance of a job. In such usage scenario, we don't need a job to be serializable. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
