Hello!
This looked sensible to me so I went forward and merged this change.
Regards,
--
Ilya Kasnacheev
пн, 25 мар. 2019 г. в 17:59, Denis Mekhanikov :
> Folks,
>
> I prepared a patch for the second ticket:
> https://github.com/apache/ignite/pull/6177
> Ilya is concerned, that if you had
Folks,
I prepared a patch for the second ticket:
https://github.com/apache/ignite/pull/6177
Ilya is concerned, that if you had some JAR files, lying next to your GARs
in a repository, which is referred to over UriDeploymentSpi, then these
JARs will now be loaded as well. So, this is a behaviour
I created the following tickets:
https://issues.apache.org/jira/browse/IGNITE-11379 – drop support of GARs
https://issues.apache.org/jira/browse/IGNITE-11380 – support JARs
https://issues.apache.org/jira/browse/IGNITE-11381 – document ignite.xml
file format.
Denis
ср, 20 февр. 2019 г. в 12:30,
Hello, Denis.
> This XML may contain task descriptors, but I couldn't find any
documentation on this format.
> This information can be provided in simple JAR files with the same file
structure.
I support you proposal. Let's:
1. Support jar files instead of gar.
2. Write down documentation about
Denis,
This XML may contain task descriptors, but I couldn't find any
documentation on this format.
Also it may contain a userVersion [1] parameter, which can be used to force
tasks redeployment in some cases.
This information can be provided in simple JAR files with the same file
structure.
Denis,
What was the purpose of having XML and other files within the GARs? Guess
it was somehow versioning related - you might have several tasks of the
same class but different versions running in a cluster.
-
Denis
On Tue, Feb 19, 2019 at 8:40 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Yes, I
Hello!
Yes, I think we should accept plain JARs if anybody needs this at all.
Might still keep meta info support for compatibility.
Regards,
--
Ilya Kasnacheev
вт, 19 февр. 2019 г. в 19:38, Denis Mekhanikov :
> Hi!
>
> There is a feature in Ignite called DeploymentSpi [1], that allows adding
Hi!
There is a feature in Ignite called DeploymentSpi [1], that allows adding
and changing implementation of compute tasks without nodes' downtime.
The only usable implementation right now is UriDeploymentSpi [2], which
lets you provide classes of compute tasks packaged as an archive of a
special
