Hello! In development environment one can just run Java from /var/lib/ignite (makes total sense) and will immediately get almost correct behavior (well, data will be stored to /var/lib/ignite/ignite/work)
However, I still think that we should write to user.dir/ignite and not just user.dir since current directory is often crowded. Fellows, anyone who is against using user.dir? Please share your concerns. Regards, -- Ilya Kasnacheev пн, 26 авг. 2019 г. в 12:17, Nikolay Izhikov <nizhi...@apache.org>: > Ilya, > > > We are talking about development scenario where you have embedded > database > > in your project and it has to write data somewhere. > > Why it should differs from production case? > I think we should be as close to production setup as we can. > > > /var/lib/ignite is certainly not writable by user's development projects. > > mysql, postgresql require some setup in dev env. > Why Ignite should differs from it? > > Please, note, we are talking about scenario when user enable PDS-mode for > some cache. > For in-memory case, no setup required. > > > ~/ignite and descendants look like a good compromise > > Not for me :) > > > Writing to user.dir/ignite, i.e. current work dir, looks equally good > > Current work dir in dev env looks good for me. > > > В Пн, 26/08/2019 в 12:06 +0300, Ilya Kasnacheev пишет: > > Hello! > > > > We are talking about development scenario where you have embedded > database > > in your project and it has to write data somewhere. > > > > /var/lib/ignite is certainly not writable by user's development projects. > > > > We could use ~/.config/ignite, which is pure UNIX way today, but I object > > against potential writing of gigabytes of WAL & PDS into user's .config. > > ~/ignite and descendants look like a good compromise. Writing to > > user.dir/ignite, i.e. current work dir, looks equally good. I will > create a > > ticket about it. > > > > Regards, >
