[jira] [Commented] (IGNITE-6261) ODBC support for Mac OSX
[ https://issues.apache.org/jira/browse/IGNITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156719#comment-16156719 ] Pranas Baliuka commented on IGNITE-6261: Only using clang Will not help, kernel API is bit different ... > ODBC support for Mac OSX > > > Key: IGNITE-6261 > URL: https://issues.apache.org/jira/browse/IGNITE-6261 > Project: Ignite > Issue Type: Bug > Components: odbc, sql >Affects Versions: 2.1 > Environment: Analytics >Reporter: Pranas Baliuka >Assignee: Igor Sapego > Labels: usability > Fix For: 2.3 > > > In order for Ignite to be useful in analytics environment (accessing data via > R / Most reporting engines), the ODBC access is required. > Analyst do use Mac OSX (not only Linux/Windows). > The current ODBC driver is not compilable on OSX due to 1-2 different kernel > API functions. > Similar incompatibility issues are already resolved in similar projects using > conditional macros in C language. i.e. it may not be a big challenge to make > it work. > Thanks for planning and considerations! > PS: > For my use case the issue is a Blocker, because rJAVA is dead (requires Java > 6 installation on Mac OSX) and even with rJAVA , the JDBC implementation is > not working for R (class cast exceptions). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6261) ODBC support for Mac OSX
[
https://issues.apache.org/jira/browse/IGNITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156294#comment-16156294
]
Pranas Baliuka commented on IGNITE-6261:
It's {{pthread_condattr_setclock(&attr, CLOCK_MONOTONIC)}}
{quote}
Imin:odbc pranas$ glibtoolize && aclocal && autoheader && automake
--add-missing && autoreconf
glibtoolize: putting auxiliary files in '.'.
glibtoolize: linking file './ltmain.sh'
glibtoolize: putting macros in 'm4'.
glibtoolize: linking file 'm4/libtool.m4'
glibtoolize: linking file 'm4/ltoptions.m4'
glibtoolize: linking file 'm4/ltsugar.m4'
glibtoolize: linking file 'm4/ltversion.m4'
glibtoolize: linking file 'm4/lt~obsolete.m4'
aclocal: error: 'configure.ac' is required
Imin:odbc pranas$ pwd
/Users/pranas/Downloads/ignite-ignite-2.1/modules/platforms/cpp/odbc
Imin:odbc pranas$ cd ..
Imin:cpp pranas$ glibtoolize && aclocal && autoheader && automake --add-missing
&& autoreconf
glibtoolize: putting auxiliary files in '.'.
glibtoolize: linking file './ltmain.sh'
glibtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
glibtoolize: linking file 'm4/libtool.m4'
glibtoolize: linking file 'm4/ltoptions.m4'
glibtoolize: linking file 'm4/ltsugar.m4'
glibtoolize: linking file 'm4/ltversion.m4'
glibtoolize: linking file 'm4/lt~obsolete.m4'
configure.ac:36: installing './ar-lib'
configure.ac:35: installing './compile'
configure.ac:24: installing './config.guess'
configure.ac:24: installing './config.sub'
configure.ac:28: installing './install-sh'
configure.ac:28: installing './missing'
binary/Makefile.am: installing './depcomp'
Imin:cpp pranas$ ./configure --enable-odbc --disable-node --disable-core
checking build system type... x86_64-apple-darwin16.7.0
checking host system type... x86_64-apple-darwin16.7.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... rm: core: is a directory
yes
checking whether gcc accepts -g... rm: core: is a directory
yes
checking for gcc option to accept ISO C89... rm: core: is a directory
none needed
checking whether gcc understands -c and -o together... rm: core: is a directory
yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for ar... ar
checking the archiver (ar) interface... rm: core: is a directory
ar
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc...
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
checking if the linker
(/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld)
is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking how to convert x86_64-apple-darwin16.7.0 file names to
x86_64-apple-darwin16.7.0 format... func_convert_file_noop
checking how to convert x86_64-apple-darwin16.7.0 file names to toolchain
format... func_convert_file_noop
checking for
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ld
option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for g++... g++
checking whether we are using the GNU C++ compiler... rm: core: is a directory
yes
checking whether g++ accepts -g... rm: core: is a directory
yes
checking dependency style of g++... gcc3
checking for archiver @FILE support... rm: core: is a directory
no
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking for dsymutil... dsymutil
[jira] [Created] (IGNITE-6261) ODBC support for Mac OSX
Pranas Baliuka created IGNITE-6261: -- Summary: ODBC support for Mac OSX Key: IGNITE-6261 URL: https://issues.apache.org/jira/browse/IGNITE-6261 Project: Ignite Issue Type: Wish Components: odbc Affects Versions: 2.1 Environment: Analytics Reporter: Pranas Baliuka Priority: Critical In order for Ignite to be useful in analytics environment (accessing data via R / Most reporting engines), the ODBC access is required. Analyst do use Mac OSX (not only Linux/Windows). The current ODBC driver is not compilable on OSX due to 1-2 different kernel API functions. Similar incompatibility issues are already resolved in similar projects using conditional macros in C language. i.e. it may not be a big challenge to make it work. Thanks for planning and considerations! PS: For my use case the issue is a Blocker, because rJAVA is dead (requires Java 6 installation on Mac OSX) and even with rJAVA , the JDBC implementation is not working for R (class cast exceptions). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6220) Values of types int and long[] are not delivered via JDBC
[ https://issues.apache.org/jira/browse/IGNITE-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranas Baliuka updated IGNITE-6220: --- Attachment: Screen Shot 2017-08-30 at 16.19.25.png > Values of types int and long[] are not delivered via JDBC > - > > Key: IGNITE-6220 > URL: https://issues.apache.org/jira/browse/IGNITE-6220 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.1 >Reporter: Pranas Baliuka > Labels: arrays > Attachments: Screen Shot 2017-08-30 at 16.19.25.png > > > I've tried Low GC prototype to populate collocated server node without > replication and access it via JDBC. > Issues detected: > * The JDBC column "TIME" with type long[] is not delivered; > * Duplicate entries in the result set; > * Key column of type int is used for filtering, but not delivered to the JDBC > Record set. > To reproduce: > [Git:https://github.com/pranasblk/ignite-not-flushing/tree/MIssingJDBCTypes] > * Run IgniteNode main > * Run JDBC main / or connect via favourite JDBC supporting client -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6220) Values of types int and long[] are not delivered via JDBC
[ https://issues.apache.org/jira/browse/IGNITE-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranas Baliuka updated IGNITE-6220: --- Component/s: jdbc > Values of types int and long[] are not delivered via JDBC > - > > Key: IGNITE-6220 > URL: https://issues.apache.org/jira/browse/IGNITE-6220 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.1 >Reporter: Pranas Baliuka > Labels: arrays > > I've tried Low GC prototype to populate collocated server node without > replication and access it via JDBC. > Issues detected: > * The JDBC column "TIME" with type long[] is not delivered; > * Duplicate entries in the result set; > * Key column of type int is used for filtering, but not delivered to the JDBC > Record set. > To reproduce: > [Git:https://github.com/pranasblk/ignite-not-flushing/tree/MIssingJDBCTypes] > * Run IgniteNode main > * Run JDBC main / or connect via favourite JDBC supporting client -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6220) Values of types int and long[] are not delivered via JDBC
[ https://issues.apache.org/jira/browse/IGNITE-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranas Baliuka updated IGNITE-6220: --- Labels: arrays (was: ) > Values of types int and long[] are not delivered via JDBC > - > > Key: IGNITE-6220 > URL: https://issues.apache.org/jira/browse/IGNITE-6220 > Project: Ignite > Issue Type: Bug > Components: jdbc >Affects Versions: 2.1 >Reporter: Pranas Baliuka > Labels: arrays > > I've tried Low GC prototype to populate collocated server node without > replication and access it via JDBC. > Issues detected: > * The JDBC column "TIME" with type long[] is not delivered; > * Duplicate entries in the result set; > * Key column of type int is used for filtering, but not delivered to the JDBC > Record set. > To reproduce: > [Git:https://github.com/pranasblk/ignite-not-flushing/tree/MIssingJDBCTypes] > * Run IgniteNode main > * Run JDBC main / or connect via favourite JDBC supporting client -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6220) Values of types int and long[] are not delivered via JDBC
[ https://issues.apache.org/jira/browse/IGNITE-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranas Baliuka updated IGNITE-6220: --- Affects Version/s: 2.1 > Values of types int and long[] are not delivered via JDBC > - > > Key: IGNITE-6220 > URL: https://issues.apache.org/jira/browse/IGNITE-6220 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.1 >Reporter: Pranas Baliuka > > I've tried Low GC prototype to populate collocated server node without > replication and access it via JDBC. > Issues detected: > * The JDBC column "TIME" with type long[] is not delivered; > * Duplicate entries in the result set; > * Key column of type int is used for filtering, but not delivered to the JDBC > Record set. > To reproduce: > [Git:https://github.com/pranasblk/ignite-not-flushing/tree/MIssingJDBCTypes] > * Run IgniteNode main > * Run JDBC main / or connect via favourite JDBC supporting client -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6220) Values of types int and long[] are not delivered via JDBC
Pranas Baliuka created IGNITE-6220: -- Summary: Values of types int and long[] are not delivered via JDBC Key: IGNITE-6220 URL: https://issues.apache.org/jira/browse/IGNITE-6220 Project: Ignite Issue Type: Bug Reporter: Pranas Baliuka I've tried Low GC prototype to populate collocated server node without replication and access it via JDBC. Issues detected: * The JDBC column "TIME" with type long[] is not delivered; * Duplicate entries in the result set; * Key column of type int is used for filtering, but not delivered to the JDBC Record set. To reproduce: [Git:https://github.com/pranasblk/ignite-not-flushing/tree/MIssingJDBCTypes] * Run IgniteNode main * Run JDBC main / or connect via favourite JDBC supporting client -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6207) Create documentations for Low GC usage
[
https://issues.apache.org/jira/browse/IGNITE-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranas Baliuka updated IGNITE-6207:
---
Summary: Create documentations for Low GC usage (was: Low GC inserting
bulk of new entries)
> Create documentations for Low GC usage
> --
>
> Key: IGNITE-6207
> URL: https://issues.apache.org/jira/browse/IGNITE-6207
> Project: Ignite
> Issue Type: New Feature
>Reporter: Pranas Baliuka
>Priority: Trivial
>
> It would be nice to have ability to keep buffer of mutable objects and reuse
> objects as container for API.
> Proposed API e.g. {{forceAddOrReplace(Iterator> entry)}} (or
> even better visitor pattern) where objects serialized but owners ship stays
> on client i.e. Ignite does not keep references to the objects provide between
> different itterator.next invocation.
> If feature is already available e.g. if {{streamer.keepBinary(true);}} forces
> to take ownership of the object content without keeping reference please
> provide guidelines got to achieve Low GC.
> Thanks
> P
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6207) Low GC inserting bulk of new entries
[
https://issues.apache.org/jira/browse/IGNITE-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranas Baliuka updated IGNITE-6207:
---
Priority: Trivial (was: Critical)
> Low GC inserting bulk of new entries
>
>
> Key: IGNITE-6207
> URL: https://issues.apache.org/jira/browse/IGNITE-6207
> Project: Ignite
> Issue Type: New Feature
>Reporter: Pranas Baliuka
>Priority: Trivial
>
> It would be nice to have ability to keep buffer of mutable objects and reuse
> objects as container for API.
> Proposed API e.g. {{forceAddOrReplace(Iterator> entry)}} (or
> even better visitor pattern) where objects serialized but owners ship stays
> on client i.e. Ignite does not keep references to the objects provide between
> different itterator.next invocation.
> If feature is already available e.g. if {{streamer.keepBinary(true);}} forces
> to take ownership of the object content without keeping reference please
> provide guidelines got to achieve Low GC.
> Thanks
> P
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6207) Low GC inserting bulk of new entries
[
https://issues.apache.org/jira/browse/IGNITE-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranas Baliuka updated IGNITE-6207:
---
Description:
It would be nice to have ability to keep buffer of mutable objects and reuse
objects as container for API.
Proposed API e.g. {{forceAddOrReplace(Iterator> entry)}} (or
even better visitor pattern) where objects serialized but owners ship stays on
client i.e. Ignite does not keep references to the objects provide between
different itterator.next invocation.
If feature is already available e.g. if {{streamer.keepBinary(true);}} forces
to take ownership of the object content without keeping reference please
provide guidelines got to achieve Low GC.
Thanks
P
was:
It would be nice to have ability to keep buffer of mutable objects and reuse
objects as container for API.
Currently looks like there's no way to have a latch/flush checkpoint and forced
to create new objects for Key/Value pair.
Proposed API e.g. {{forceAddOrReplace(Iterator> entry)}} (or
even better visitor pattern) where objects serialized but owners ship stays on
client i.e. Ignite does not keep references to the objects provide between
different itterator.next invocation.
Clarification:
I know it sounds weird for enterprise developers (tolerant to extremely large
latencies e.g. 100ms), but current system can not be practically applied for
medium latency systems in finance.
> Low GC inserting bulk of new entries
>
>
> Key: IGNITE-6207
> URL: https://issues.apache.org/jira/browse/IGNITE-6207
> Project: Ignite
> Issue Type: New Feature
>Reporter: Pranas Baliuka
>
> It would be nice to have ability to keep buffer of mutable objects and reuse
> objects as container for API.
> Proposed API e.g. {{forceAddOrReplace(Iterator> entry)}} (or
> even better visitor pattern) where objects serialized but owners ship stays
> on client i.e. Ignite does not keep references to the objects provide between
> different itterator.next invocation.
> If feature is already available e.g. if {{streamer.keepBinary(true);}} forces
> to take ownership of the object content without keeping reference please
> provide guidelines got to achieve Low GC.
> Thanks
> P
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6207) Low GC inserting bulk of new entries
[
https://issues.apache.org/jira/browse/IGNITE-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranas Baliuka updated IGNITE-6207:
---
Priority: Critical (was: Major)
> Low GC inserting bulk of new entries
>
>
> Key: IGNITE-6207
> URL: https://issues.apache.org/jira/browse/IGNITE-6207
> Project: Ignite
> Issue Type: New Feature
>Reporter: Pranas Baliuka
>Priority: Critical
>
> It would be nice to have ability to keep buffer of mutable objects and reuse
> objects as container for API.
> Proposed API e.g. {{forceAddOrReplace(Iterator> entry)}} (or
> even better visitor pattern) where objects serialized but owners ship stays
> on client i.e. Ignite does not keep references to the objects provide between
> different itterator.next invocation.
> If feature is already available e.g. if {{streamer.keepBinary(true);}} forces
> to take ownership of the object content without keeping reference please
> provide guidelines got to achieve Low GC.
> Thanks
> P
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (IGNITE-6207) Low GC inserting bulk of new entries
[
https://issues.apache.org/jira/browse/IGNITE-6207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pranas Baliuka updated IGNITE-6207:
---
Summary: Low GC inserting bulk of new entries (was: Low GC inserting of
new entries)
> Low GC inserting bulk of new entries
>
>
> Key: IGNITE-6207
> URL: https://issues.apache.org/jira/browse/IGNITE-6207
> Project: Ignite
> Issue Type: New Feature
>Reporter: Pranas Baliuka
>
> It would be nice to have ability to keep buffer of mutable objects and reuse
> objects as container for API.
> Currently looks like there's no way to have a latch/flush checkpoint and
> forced to create new objects for Key/Value pair.
> Proposed API e.g. {{forceAddOrReplace(Iterator> entry)}} (or
> even better visitor pattern) where objects serialized but owners ship stays
> on client i.e. Ignite does not keep references to the objects provide between
> different itterator.next invocation.
> Clarification:
> I know it sounds weird for enterprise developers (tolerant to extremely large
> latencies e.g. 100ms), but current system can not be practically applied for
> medium latency systems in finance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (IGNITE-6206) IgniteDataStreamer flush() is not working
[ https://issues.apache.org/jira/browse/IGNITE-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pranas Baliuka resolved IGNITE-6206. Resolution: Invalid > IgniteDataStreamer flush() is not working > - > > Key: IGNITE-6206 > URL: https://issues.apache.org/jira/browse/IGNITE-6206 > Project: Ignite > Issue Type: Test >Reporter: Pranas Baliuka >Priority: Blocker > Labels: newbie > > Dear Ignite experts, > I'm total newbie at Ignite and trying to interpret JavaDoc of > IgniteDataStreamer and test. > Summary of the test at forum: > http://apache-ignite-users.70518.x6.nabble.com/Why-DataStreamer-flush-is-not-flushing-td16466.html > Attempt to have checkpoint to flush data to cache from IgniteDataStreamer are > not working: > * Restricted buffers; > * Time based flushing; > * Explicit flushig. > Test project - https://github.com/pranasblk/ignite-not-flushing > Let me know if it is by design. Otherwise point to documentation explaining > how to do flusing ... > Thanks > P -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6207) Low GC inserting of new entries
Pranas Baliuka created IGNITE-6207:
--
Summary: Low GC inserting of new entries
Key: IGNITE-6207
URL: https://issues.apache.org/jira/browse/IGNITE-6207
Project: Ignite
Issue Type: New Feature
Reporter: Pranas Baliuka
It would be nice to have ability to keep buffer of mutable objects and reuse
objects as container for API.
Currently looks like there's no way to have a latch/flush checkpoint and forced
to create new objects for Key/Value pair.
Proposed API e.g. {{forceAddOrReplace(Iterator> entry)}} (or
even better visitor pattern) where objects serialized but owners ship stays on
client i.e. Ignite does not keep references to the objects provide between
different itterator.next invocation.
Clarification:
I know it sounds weird for enterprise developers (tolerant to extremely large
latencies e.g. 100ms), but current system can not be practically applied for
medium latency systems in finance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6206) IgniteDataStreamer flush() is not working
Pranas Baliuka created IGNITE-6206: -- Summary: IgniteDataStreamer flush() is not working Key: IGNITE-6206 URL: https://issues.apache.org/jira/browse/IGNITE-6206 Project: Ignite Issue Type: Test Reporter: Pranas Baliuka Priority: Blocker Dear Ignite experts, I'm total newbie at Ignite and trying to interpret JavaDoc of IgniteDataStreamer and test. Summary of the test at forum: http://apache-ignite-users.70518.x6.nabble.com/Why-DataStreamer-flush-is-not-flushing-td16466.html Attempt to have checkpoint to flush data to cache from IgniteDataStreamer are not working: * Restricted buffers; * Time based flushing; * Explicit flushig. Test project - https://github.com/pranasblk/ignite-not-flushing Let me know if it is by design. Otherwise point to documentation explaining how to do flusing ... Thanks P -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6164) H2 dependency is not resolved from ignite-indexing:2.1.0
[
https://issues.apache.org/jira/browse/IGNITE-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138267#comment-16138267
]
Pranas Baliuka commented on IGNITE-6164:
It's not a bit thing to add missing m2 dependency (minor), but ideally it
should be resolved as transitive runtime dependency.
P.S. some plans for upgrading to Gradle?
On Aug 23, 2017 8:57 PM, "Vladimir Ozerov (JIRA)" wrote:
[ https://issues.apache.org/jira/browse/IGNITE-6164?page=
com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel&focusedCommentId=16138222#comment-16138222 ]
Vladimir Ozerov commented on IGNITE-6164:
-
[~pranas], I am not sure I understand what is the problem. Do you have
difficulties in resolving certain artifacts?
https://github.com/srecon/ignite-book-code-samples with dependecies:
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
> H2 dependency is not resolved from ignite-indexing:2.1.0
>
>
> Key: IGNITE-6164
> URL: https://issues.apache.org/jira/browse/IGNITE-6164
> Project: Ignite
> Issue Type: Bug
>Reporter: Pranas Baliuka
>Priority: Minor
>
> I've tested the first code sample from Ignite book code
> https://github.com/srecon/ignite-book-code-samples with dependecies:
> {code}
>
> UTF-8
> 2.1.0
>
>
>
> junit
> junit
> 3.8.1
> test
>
>
> org.apache.ignite
> ignite-core
> ${ignite.version}
>
>
> org.apache.ignite
> ignite-spring
>
>
> org.apache.ignite
> ignite-indexing
>
>
> {code}
> Runtime exception indicates what transitive dependency:
> {code}
>
> com.h2database
> h2
> 1.4.195
> runtime
>
> {code}
> is not resolved from the {{ignite-indexing}} . Consider fixing
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6164) H2 dependency is not resolved from ignite-indexing:2.1.0
Pranas Baliuka created IGNITE-6164:
--
Summary: H2 dependency is not resolved from ignite-indexing:2.1.0
Key: IGNITE-6164
URL: https://issues.apache.org/jira/browse/IGNITE-6164
Project: Ignite
Issue Type: Bug
Reporter: Pranas Baliuka
Priority: Minor
I've tested the first code sample from Ignite book code
https://github.com/srecon/ignite-book-code-samples with dependecies:
{code}
UTF-8
2.1.0
junit
junit
3.8.1
test
org.apache.ignite
ignite-core
${ignite.version}
org.apache.ignite
ignite-spring
org.apache.ignite
ignite-indexing
{code}
Runtime exception indicates what transitive dependency:
{code}
com.h2database
h2
1.4.195
runtime
{code}
is not resolved from the {{ignite-indexing}} . Consider fixing
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
