[JBoss JIRA] (ISPN-2575) KeyTransformer registration is required on all nodes of the cluster, in case of custom keys
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2575:
--------------------------------
Assignee: Adrian Nistor (was: Sanne Grinovero)
> KeyTransformer registration is required on all nodes of the cluster, in case of custom keys
> -------------------------------------------------------------------------------------------
>
> Key: ISPN-2575
> URL: https://issues.jboss.org/browse/ISPN-2575
> Project: Infinispan
> Issue Type: Enhancement
> Components: Querying
> Affects Versions: 5.2.0.Beta5
> Reporter: Anna Manukyan
> Assignee: Adrian Nistor
> Attachments: ClusteredCacheTest.java
>
>
> The case is the following:
> I have a clustered cache on which I want to perform a search. I'm doing the following:
> I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception:
> java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer
> When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager.
> The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer()
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1 week, 2 days
[JBoss JIRA] (ISPN-4693) Locks acquired before a partition will never be released
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4693?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4693:
-----------------------------------------------
Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1155692|https://bugzilla.redhat.com/show_bug.cgi?id=1155692] from ON_QA to VERIFIED
> Locks acquired before a partition will never be released
> --------------------------------------------------------
>
> Key: ISPN-4693
> URL: https://issues.jboss.org/browse/ISPN-4693
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 6.0.2.Final
> Reporter: Erik Salter
> Assignee: Dan Berindei
> Fix For: 7.0.0.CR2, 7.0.0.Final
>
>
> Consider the following case:
> 1. A prepares a transaction for key K on nodes B and C.
> 2. The primary owner B acquires and registers this lock.
> 3. The cluster partitions and A,C remain in partition one, and B in a separate partition.
> 4. The transaction rolls back. However, since B left the cluster, the rollback will not be sent to B.
> 5. B rejoins the cluster. It still has a lock acquired for key K.
> This can lead to a lock being acquired indefinitely.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-5902) Stream iterator/forEach should use configured Equivalence
by William Burns (JIRA)
William Burns created ISPN-5902:
-----------------------------------
Summary: Stream iterator/forEach should use configured Equivalence
Key: ISPN-5902
URL: https://issues.jboss.org/browse/ISPN-5902
Project: Infinispan
Issue Type: Bug
Components: Core
Reporter: William Burns
Assignee: William Burns
The stream methods to use iterator and forEach do not use equivalence when storing their keys. This should be done to make sure entries are not repeated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-5791) Query DSL : Projecting a Date field multiple times will render it as string
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5791?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5791:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Query DSL : Projecting a Date field multiple times will render it as string
> ---------------------------------------------------------------------------
>
> Key: ISPN-5791
> URL: https://issues.jboss.org/browse/ISPN-5791
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha1
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Beta1, 8.0.2.Final
>
>
> Adding this in QueryDslConditionsTest fails. The second date projection is a String instead of being a Date. First projection is OK. The problem is gone if cache is not indexed, which makes me think it is more of a problem in CacheQuery.
> {code}
> public void testDuplicateDateProjection() throws Exception {
> QueryFactory qf = getQueryFactory();
> Query q = qf.from(getModelFactory().getTransactionImplClass())
> .select("id", "date", "date")
> .having("description").eq("Hotel")
> .toBuilder().build();
> List<Object[]> list = q.list();
> assertEquals(1, list.size());
> assertEquals(1, list.size());
> assertEquals(3, list.get(0).length);
> assertEquals(3, list.get(0)[0]);
> assertEquals(makeDate("2013-02-27"), list.get(0)[1]);
> assertEquals(makeDate("2013-02-27"), list.get(0)[2]);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ISPN-5873) Allow non-stored fields to be projected in DSL based queries
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-5873?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-5873:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Allow non-stored fields to be projected in DSL based queries
> ------------------------------------------------------------
>
> Key: ISPN-5873
> URL: https://issues.jboss.org/browse/ISPN-5873
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Beta1, 8.0.2.Final
>
>
> Currently if a field is indexed but it is not stored it cannot be used in a projection but if the field is not indexed it can be used in projections due to the way hybrid queries work. This uneven handling should disappear. All fields should be allowed for projections and if they are stored we should take advantage of that.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years