[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    [jira] [Commented] (JAMES-2038) Datastax driver mess-up when mixing paging, futures and collects.
From:       "Tellier Benoit (JIRA)" <server-dev () james ! apache ! org>
Date:       2017-05-29 9:51:04
Message-ID: JIRA.13075500.1496022638000.314041.1496051464165 () Atlassian ! JIRA
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/JAMES-2038?page=com.atlassian.jira.plugin. \
system.issuetabpanels:comment-tabpanel&focusedCommentId=16028174#comment-16028174 ] 

Tellier Benoit commented on JAMES-2038:
---------------------------------------

https://datastax-oss.atlassian.net/browse/JAVA-1480 opened on Datastax driver

> Datastax driver mess-up when mixing paging, futures and collects.
> -----------------------------------------------------------------
> 
> Key: JAMES-2038
> URL: https://issues.apache.org/jira/browse/JAMES-2038
> Project: James Server
> Issue Type: Improvement
> Reporter: Tellier Benoit
> 
> Apparently paging is not handled well by the driver when collecting the stream of \
> result in a future. The following query is obtained with a SELECT on a mailbox with \
> 5500 RECENT messages (so over the paging size of 5000): {code:java}
> [cluster1] [/172.17.0.1:9042] Query error after 5014 ms: [1 bound values] SELECT \
> recent_mesage_uid FROM mailboxRecents WHERE mailboxId=:mailboxId; \
> [mailboxid:a7914ae0-f3a1-11e6-88e7-ddd22b16a7b9] {code}
> We should change the return type to overpass this limit. We should also audit code \
> to ensure we don't have this bug in other places.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]