Hello! Here's my list of improvements for AI package: - Make sqlline.sh callable from command line (PATH). E.g. symlink it as /usr/bin/sqlline-ignite, make sure it works. - Fix control.sh and visor-cmd, expose them too. - Allow specifying of JDK implementation and JDK arguments for Apache Ignite startup. Preferably on per configuration basis. - Allow adding-removing "modules" to classpath of Ignite - again, preferably on per configuration basis. E.g. what happens if I want to turn ON geospatial/ - [OPTIONAL] Ship Apache Ignite with a special config which only listens on localhost. This is for lazy people who can get into trouble by installing package without looking without security implications.
With regards to splitting package, I think we could have a few of them (a-i-core, a-i-doc, a-i-c++, a-i-.net) but I don't think we need to have a half dozen of those right away. This was mostly realised as an antipattern. Regards, -- Ilya Kasnacheev 2018-06-04 17:43 GMT+03:00 Petr Ivanov <mr.wei...@gmail.com>: > Igniters! > > > Apache Ignite 2.5 is released and for the first time in it’s history is > shipped in both RPM and DEB packages. > And, I think, it is time to discuss the future roadmap of Apache Ignite in > Linux packages initiative. > > For the first “feature” I would suggest splitting of the packages on > smaller parts (at least the same way it was prepare but declined in 2.5) — > we can continue discussion here. > Also it would be great to hear community thoughts about other possible > improvements of delivering Apache Ignite in packages.
