Dmitriy, Agree. The documentation is already there. https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence <https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence>
However, the documentation is presently based on the legacy schema-import tool. It’s reasonable to refine the documentation relying on a similar Web Console capability. The question is do we want to keep maintaining the schema-import’s documentation at least for some time or this tool has to be fully discontinued in favor of Web Console? Also, Dmitriy please take a look at the following. The integrations’ documentation style is absolutely different from the ones we have for other documentations domains >> Dmitriy, looks like we have to upgrade readme.io subscription to >> “Developer Hub” for the new documentation domain because now there is now >> way to change the appearance. Could >> you handle this? — Denis > On Nov 29, 2016, at 10:01 PM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > > Denis, do you think RDBMS integrations should be there as well? > > On Wed, Nov 30, 2016 at 4:22 AM, Denis Magda <dma...@apache.org> wrote: > >> Igniters, >> >> Ignite can already boast about a number of integrations it has with a >> other products and technologies. Up to this point all the integrations were >> documented on our main readme.io <http://readme.io/> making the overall >> documentation a bit messy. >> >> I’ve decoupled the integrations from the core modules by moving them to a >> new documentation domain “Apache Ignite Integrations” < >> https://apacheignite-mix.readme.io/docs>. As a result integrations as >> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the streamers >> reside there. >> >> Dmitriy, looks like we have to upgrade readme.io subscription to >> “Developer Hub” for the new documentation domain because now there is now >> way to change the appearance. Appearance themes settings are poor. Could >> you handle this? >> >> — >> Denis
