merging all the github projects back?
by Mircea Markus
Hi guys,
Given all the compiling problems we had since we've split in multiple github repos (server, stores and embedded) makes me think that the split wasn't such a great idea after all( and that I was hmm, wrong). Shall we move everything back into a single repo? We can still keep different CI runs for cache stores, server etc, but at least all this builds will compile everything.
wdyt?
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
12 years, 1 month
Infinispan server REST API functionality question
by Jiri Holusa
Hi,
Galder suggested posting this question here, so here it comes. :)
I'm adding tests for ISPN server REST endpoint and I'm wondering if following feature should be supported. In existing tests (IntegrationTests.scala) I see this test case: put entry directly into cache (via RemoteCacheManager) then retrieve via REST with header Accept: application/json or application/xml. Returns nice json or xml structure of the object, just as expected.
I tried to do the same thing, but now put the entry via REST (the only difference to previous case, not directly) and then retrieve via REST with various Accept headers. But it returns me the Content-Type which was set during the put and also the same content. For instance: put (Content-type: application/x-java-serialized-object) and get (Accept: application/json) => still returns application/x-java-serialized-object.
I'm wondering if there should also be some sort of transformation or this is not supported or maybe I'm doing something wrong.
I would appreciate any help, sorry for bothering you, guys.
Jirka Holusa
12 years, 1 month
Infinispan 6.0.0.Final is out!
by Adrian Nistor
Dear Infinispan community,
We're pleased to announce the final release of Infinispan 6.0
"Infinium". Asannounced
<http://infinispan.blogspot.co.uk/2013/05/infinispan-to-adopt-apache-softw...>,
this is the first Infinispan stable version to be released under the
terms ofApache License v2.0
<http://www.apache.org/licenses/LICENSE-2.0.html>.
This release brings some highly demanded features besides many stability
enhancements and bug fixes:
*
Support for remote query
<http://blog.infinispan.org/2013/09/embedded-and-remote-query-in-infinispa...>.
It is now possible for the HotRod clients to query an Infinispan
grid using a new expressive query DSL. This querying functionality
is built on top of Apache Lucene and Google Protobuf and lays the
foundation for storing information and querying an Infinispan server
in a language neutral manner. The Java HotRod client has already
been enhanced to support this, the soon-to-be announced C++ HotRod
client will also contain this functionality (initially for
write/read, then full blown querying).
*
C++ HotRod client. Allows C++ applications to read and write
information from an Infinispan server. This is a fully fledged
HotRod client that is topology (level 2) and consistent hash aware
(level 3) and will be released in the following days. Some features
(such as Remote Query and SSL support) will be developed during the
next iteration so that it maintains feature parity with its Java
counterpart.
*
Better persistence integration. We've revisited the entire cache
loader API and we're quite pleased with the result: the new
Persistence API
<http://blog.infinispan.org/2013/09/new-persistence-api-in-infinispan.html>brought
by Infinispan 6.0 supports parallel iteration of the stored entries,
reduces the overall serialization overhead and also is aligned with
the JSR-107 <http://jcp.org/en/jsr/detail?id=107>specification,
which makes implementations more portable.
*
A more efficient FileCacheStore implementation
<http://blog.infinispan.org/2013/07/faster-file-cache-store-no-extra.html>.
This file store is built with efficiency in mind: it outperforms the
existing file store with up to 2 levels of magnitude. This comes at
a cost though, as keys need to be kept in memory. Thanks to Karsten
Blees <https://github.com/kblees>for contributing this!
*
Support for heterogeneous clusters
<http://blog.infinispan.org/2013/09/heterogenous-clusters-with-infinispan.htm>.
Up to this release, every member of the cluster owns an equal share
of the cluster's data. This doesn't work well if one machine is more
powerful than the other cluster participants. This functionality
allows specifying the amount of data, compared with the average,
held by a particular machine.
*
A new set of usage and performance statistics
<https://issues.jboss.org/browse/ISPN-2861>developed within the
scope of the CloudTM project<https://issues.jboss.org/browse/ISPN-3234>.
*
JCache <https://issues.jboss.org/browse/ISPN-3234>(JSR-107)
implementation upgrade. First released in Infinispan 5.3.0, the
standard caching support is now upgraded to version 1.0.0-PFD.
For a complete list of features included in this release please refer to
the release notes
<https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310799&versi...>.
The user documentation for this release has been revamped and migrated
to the new website <http://infinispan.org/documentation/>- we think it
looks much better and hope you'll like it too!
This release has spread over a period of 5 months: a sustained effort
from the core development team, QE team and our growing community - a
BIG thanks to everybody involved! Please visit our downloads
<http://infinispan.org/download/>section to find the latest release.
Also if you have any questions please check our forums
<http://infinispan.org/community/>, our mailing lists
<https://lists.jboss.org/mailman/listinfo/infinispan-dev>or ping us
directly on IRC <irc://irc.freenode.org/infinispan>.
Cheers,
Adrian
12 years, 1 month
CI run for the Cpp client
by Mircea Markus
Hi,
Ion has access to my AWS account so he can launch new instances.
>From the top of my head, for the Cpp client CI we'd need:
- an RHEL5 build on every check in
- an RHEL6 build on every check in
- an Windows 7 (?) build on every check in
Same for pull every pull requests.
Work to integration with the teamcity is also need. (Ion you should have credentials for connecting to ci.infinispan.org.)
For cost reasons, these instances should only be launched when there's activity.
Please also give a cost estimate (monthly + initial) so that we can get an idea of the budget needed.
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
12 years, 1 month
Running master: some failing test
by Sanne Grinovero
Attempt 1#
Failed tests:
AsyncReplExtendedStatisticTest>BaseClusteredExtendedStatisticTest.testReplaceWithOldVal:190->BaseClusteredExtendedStatisticTest.assertCacheValue:253->MultipleCacheManagersTest.assertEventuallyEquals:554->AbstractInfinispanTest.eventually:173->AbstractInfinispanTest.eventually:45->AbstractInfinispanTest.eventually:62
expected [true] but found [false]
Attempt 2#
Failed tests:
NonTxStateTransferOverwritingValue2Test.testBackupOwnerJoiningDuringReplace:78->doTest:170
» Timeout
Attempt 3#
Failed tests:
AsyncReplExtendedStatisticTest>BaseClusteredExtendedStatisticTest.testReplaceWithOldVal:190->BaseClusteredExtendedStatisticTest.assertCacheValue:253->MultipleCacheManagersTest.assertEventuallyEquals:554->AbstractInfinispanTest.eventually:173->AbstractInfinispanTest.eventually:45->AbstractInfinispanTest.eventually:62
expected [true] but found [false]
Attempt 4#
Failed tests:
AsyncReplExtendedStatisticTest>BaseClusteredExtendedStatisticTest.testReplaceWithOldVal:190->BaseClusteredExtendedStatisticTest.assertCacheValue:253->MultipleCacheManagersTest.assertEventuallyEquals:554->AbstractInfinispanTest.eventually:173->AbstractInfinispanTest.eventually:45->AbstractInfinispanTest.eventually:62
expected [true] but found [false]
12 years, 1 month
