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 XML config format. 3. Provide some examples. Can you crate a tickets for it? ср, 20 февр. 2019 г. в 11:49, Denis Mekhanikov <[email protected]>: > 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. > There is no need to confuse people and require their packages to have a GAR > extension. > > Also if you don't specify the task descriptors, then all tasks in the file > will be registered. > So, I doubt, that anybody will bother specifying the descriptors. XML is > not very user-friendly. > This piece of configuration doesn't seem necessary to me. > > [1] > > https://apacheignite.readme.io/docs/deployment-modes#section-un-deployment-and-user-versions > > Denis > > ср, 20 февр. 2019 г. в 01:35, Denis Magda <[email protected]>: > > > 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 < > [email protected] > > > > > wrote: > > > > > 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 <[email protected] > >: > > > > > > > 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 form. And this special form is the worst part. > > > > GAR file is just like a JAR, but with some additional meta info. It > may > > > > contain an XML with description of tasks, a checksum and also > > > dependencies. > > > > > > > > We barely have any tools to build these files, and they can be > replaced > > > > with simple uber-JARs. > > > > The only tool we have right now is IgniteDeploymentGarAntTask, which > is > > > not > > > > documented anywhere, and it's supposed to be used from a > long-forgotten > > > > Apache Ant build system. > > > > > > > > I don't think we need this file format. How about we deprecate and > > remove > > > > it and make UriDeploymentSpi support plain JARs? > > > > > > > > [1] https://apacheignite.readme.io/docs/deployment-spi > > > > [2] > > > > > > > > > > > > > > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/deployment/uri/UriDeploymentSpi.html > > > > > > > > Denis > > > > > > > > > >
