John,
I am still a bit confused. I was talking about the version of the JCache
spec API, essentially only interfaces. The spec does not have any
implementation, nor implies that every project importing or depending on
the spec must be compliant with the spec.
In my view implementation and TCK com
Le 28 mars 2016 10:15, "Dmitriy Setrakyan" a écrit :
>
> John,
>
> I am still a bit confused. I was talking about the version of the JCache
spec API, essentially only interfaces. The spec does not have any
implementation, nor implies that every project importing or depending on
the spec must be co
Denis Magda created IGNITE-2899:
---
Summary: BinaryObject is deserialized before to get passed to
CacheInterceptor
Key: IGNITE-2899
URL: https://issues.apache.org/jira/browse/IGNITE-2899
Project: Ignite
Igor Sapego created IGNITE-2900:
---
Summary: CPP: Metadata update request causes Java Exception.
Key: IGNITE-2900
URL: https://issues.apache.org/jira/browse/IGNITE-2900
Project: Ignite
Issue Type
Igor Sapego created IGNITE-2901:
---
Summary: Create TeamCity configurations for C++ tests.
Key: IGNITE-2901
URL: https://issues.apache.org/jira/browse/IGNITE-2901
Project: Ignite
Issue Type: Task
Igor Sapego created IGNITE-2902:
---
Summary: CPP: Make IgniteError subclass of the std::exception.
Key: IGNITE-2902
URL: https://issues.apache.org/jira/browse/IGNITE-2902
Project: Ignite
Issue Ty
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/581
IGNITE-2900: Fixed exception on type update.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2900
Alternatively you can r
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/582
IGNITE-2902: IgniteError now implements std::exception.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2902
Alternativel
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/583
IGNITE-2897: ODBC is now disabled by default.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/isapego/ignite ignite-2897
Alternatively you can
Igniters,
Can someone check if the Geronimo JCache jar is the same as the JSR107?
http://mvnrepository.com/artifact/org.apache.geronimo.specs/geronimo-jcache_1.0_spec
We should try switching to the Geronimo JAR starting next release, as it is
licensed under Apache 2.0.
D.
Hello, Igniters,
Lately I've been working on the C++ components of Ignite and
I believe we need to rework the way we are building and shipping C++
components in Linux with Autotools.
I'll explain. Currently build process of the Apache Ignite C++ client
library looks like follows:
cd $IGNITE_HOME/
My name is Vlad.
I am from Moskow, Russia and not be native speaker Englesh.
I am newest GridGain developer and going to contribute Apache Ignite
project.
Want to sart with this bug https://issues.apache.org/jira/browse/IGNITE-2394
and try to get it the nerest.
Hi Vladimir,
That is great to hear. We have this wiki page on how one can define and
contribute their stack/service using Ambari -
https://cwiki.apache.org/confluence/display/AMBARI/How-To+Define+Stacks+and+Services
Please go through that document and let us know if you have any difficulty.
Best
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/584
IGNITE-2645 Assertion error in ATOMIC cachce for invokeAll and cache store
Fix.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashutakGG/incub
Vasiliy Sisko created IGNITE-2903:
-
Summary: Possible memory leak in offheap cache in case of
put-remove-clear.
Key: IGNITE-2903
URL: https://issues.apache.org/jira/browse/IGNITE-2903
Project: Ignite
15 matches
Mail list logo
