[JBoss JIRA] (ISPN-4396) DSL Query: right condition lost
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4396?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4396:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1108695|https://bugzilla.redhat.com/show_bug.cgi?id=1108695] from ON_QA to VERIFIED
> DSL Query: right condition lost
> -------------------------------
>
> Key: ISPN-4396
> URL: https://issues.jboss.org/browse/ISPN-4396
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.0.0.Alpha4
> Reporter: Radim Vansa
> Assignee: Adrian Nistor
> Fix For: 7.0.0.Alpha5
>
>
> Condition created through query like this:
> {code}
> Query q = qf.from(User.class)
> .not(
> qf.having("name").eq("John")
> .or(qf.having("surname").eq("Man")))
> .toBuilder().build();
> {code}
> is not correctly parsed into JPQL query; it is
> {code}
> FROM org.infinispan.query.dsl.embedded.sample_domain_model.User _gen0 WHERE NOT (_gen0.name = 'John')
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (ISPN-4654) AND over range queries does not work (indexless query)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4654?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4654:
-----------------------------------------------
Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1132121|https://bugzilla.redhat.com/show_bug.cgi?id=1132121] from ON_QA to VERIFIED
> AND over range queries does not work (indexless query)
> ------------------------------------------------------
>
> Key: ISPN-4654
> URL: https://issues.jboss.org/browse/ISPN-4654
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Affects Versions: 6.0.2.Final, 7.0.0.Beta1
> Reporter: Radim Vansa
> Assignee: Adrian Nistor
>
> Check this in QueryDslConditionsTest:
> {code}
> public void testAnd5() throws Exception {
> QueryFactory qf = getQueryFactory();
> // range queries use different code
> Query q = qf.from(getModelFactory().getUserImplClass())
> .having("id").lt(1000)
> .and().having("age").lt(1000)
> .toBuilder().build();
> List<User> list = q.list();
> assertEquals(3, list.size());
> }
> {code}
> The problem is that some subscription gets suspended and the second LT does not fire the second predicate update (and then neither the AND reevaluation).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (ISPN-4678) Trim down ExpandableMarshalledValueByteStream to the actual data length before storing in cache
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4678?page=com.atlassian.jira.plugin.... ]
Dan Berindei commented on ISPN-4678:
------------------------------------
[~mgencur] If you want to always copy the buffer to the exact size, yes, growing by 2 is probably better than 1.5. I was thinking that a growth factor of 1.5 would remove the need for some of the buffer copies, because the wasted space would be small enough.
One more thing: not all values that are serialized are stored in the data container, some are just sent to another node and discarded (e.g. if the originator is not the primary owner, in non-tx caches). In that case, it really doesn't make sense to copy the buffer, regardless of the amount of space saved.
> Trim down ExpandableMarshalledValueByteStream to the actual data length before storing in cache
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-4678
> URL: https://issues.jboss.org/browse/ISPN-4678
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Affects Versions: 7.0.0.Beta1
> Reporter: Martin Gencur
> Assignee: Martin Gencur
>
> When storeAsBinary configuration flag is used, the ExpandableMarshalledValueByteStream is used to serialize objects to byte arrays.
> However, for value size up to 4kB, almost half of the space for each cache entry can be wasted because the ByteStream is stored as is - with the additional space for future expansion.
> For value size greater than 4kB, only additional 25% of actual value size can be wasted. But as these values can be quite large, the wasted space gets bigger too.
> It is not necessary to store ExpandableMarshalledValueByteStream as is and can be shrinked to actual data size before storing in cache.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months