Thanks Alexey K! By the way, this probably will be useful for the whole community. Whenever dealing with paths, you can utilize IgniteUtils.resolveIgnitePath(...) method.
D. P.S. Given that we have 2 Alexeys, how about we call Alexey K as "AK" and Alexey G as "AG"? AK sounds way better, of course :) On Mon, Mar 23, 2015 at 8:41 AM, Alexey Kuznetsov <[email protected]> wrote: > Implemented resolve logic for properties with help of > U.resolveIgnitePath(). > > On Mon, Mar 23, 2015 at 9:35 PM, Alexey Kuznetsov <[email protected] > > > wrote: > > > Yes, you are right. > > > > On Mon, Mar 23, 2015 at 9:15 PM, Dmitriy Setrakyan < > [email protected]> > > wrote: > > > >> Guys, > >> > >> I have reviewed schema-import demo again. It got a lot better, but I > still > >> have a question about "schema-import.properties" file. > >> > >> Is there a reason why we have %IGNITE_HOME% variable used there at all, > >> like so? > >> > >> jdbc.driver.jar=%IGNITE_HOME%/libs/ignite-indexing/h2-1.3.175.jar > >> > >> Why don't we just treat the paths in exactly the same manner like in the > >> rest of the Ignite: > >> > >> - Try the path relative the root of the installation > >> - If the above failed, try the absolute path > >> > >> Can the schema-import be changed to work in such fashion? > >> > >> D. > >> > > > > > > > > -- > > Alexey Kuznetsov > > GridGain Systems > > www.gridgain.com > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >
