[JBoss JIRA] (ISPN-9693) Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9693?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9693:
-------------------------------
Fix Version/s: 10.0.0.Alpha2
(was: 10.0.0.Alpha1)
> Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
> ---------------------------------------------------------------------------
>
> Key: ISPN-9693
> URL: https://issues.jboss.org/browse/ISPN-9693
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Loaders and Stores
> Affects Versions: 9.4.1.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Alpha2
>
>
> Currently MarshalledEntryImpl is used throughout both our production and test code. Instead, we should utilise a MarshalledEntryFactory to create all MarshalledEntry instances in production and where appropriate in test classes. Furthermore, we should prevent MarshalledEntryImpl instances being created directly by users.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9714) Update CacheNotifier to return CompletionStage
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9714?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9714:
-------------------------------
Fix Version/s: 10.0.0.Alpha2
(was: 10.0.0.Alpha1)
> Update CacheNotifier to return CompletionStage
> ----------------------------------------------
>
> Key: ISPN-9714
> URL: https://issues.jboss.org/browse/ISPN-9714
> Project: Infinispan
> Issue Type: Sub-task
> Components: Core, Listeners
> Reporter: William Burns
> Assignee: William Burns
> Priority: Major
> Fix For: 10.0.0.Alpha2
>
>
> We need to update CacheNotifier to return CompletionStage for all its appropriate methods. We also need to update all the internals to use these appropriately.
> Not all notification usages may provide support non blocking, but our listener internals should support non blocking listeners for all.
> The simplest way internally is to treat all current listeners as "alien" and invoke them in the notification thread pool. If it is sync we would wait for this task to complete. We would also now allow a listener to return a CompletionStage. If this is returned we will use this operate in a non blocking way.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9745) Release fails because compatibility bundle modules don't have source jars
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9745?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9745:
-------------------------------
Fix Version/s: 10.0.0.Alpha2
(was: 10.0.0.Alpha1)
> Release fails because compatibility bundle modules don't have source jars
> -------------------------------------------------------------------------
>
> Key: ISPN-9745
> URL: https://issues.jboss.org/browse/ISPN-9745
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Alpha2, 9.4.3.Final
>
>
> Modules {{client/marshaller/protostuff/protostuff-marshaller-compatibility-bundle}} and {{client/marshaller/protostuff/protostuff-marshaller-compatibility-bundle}} are uber-jars and don't have any sources.
> Prior to the ISPN-9697 changes, a {{DEPENDENCIES.txt}} and {{LICENSES.txt}} was generated in the source directory, and a test-sources jar was created. But after those files were removed, a test-sources jar is no longer generated, and Nexus rejects the artifacts:
> {noformat}
> 11:19:37.492 [ERROR]
> 11:19:37.492 [ERROR] Nexus Staging Rules Failure Report
> 11:19:37.492 [ERROR] ==================================
> 11:19:37.492 [ERROR]
> 11:19:37.493 [ERROR] Repository "jboss_releases_staging_profile-14551" failures
> 11:19:37.493 [ERROR] Rule "sources-staging" failures
> 11:19:37.493 [ERROR] * Missing: no sources jar found in folder '/org/infinispan/infinispan-marshaller-kryo-bundle/9.4.2.Final'
> 11:19:37.493 [ERROR] * Missing: no sources jar found in folder '/org/infinispan/infinispan-marshaller-protostuff-bundle/9.4.2.Final'
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9752) JDBCStringBasedStore should disable auto commit for publish methods
by William Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-9752?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-9752:
--------------------------------
Description:
Some JDBC drivers do not do paging for result sets when auto commit is disabled, namely postgresql
https://jdbc.postgresql.org/documentation/83/query.html#query-with-cursor
There shouldn't be any drawbacks of disabling auto commit before performing the query. We wouldn't even need to rollback/commit the connection and just return it to the pool. The pool can do that for us as we don't care if it is committed as it is a read only query.
Could you please give the opportunity to disable autoCommit in order for the JDBC page size to work (even if the store is not transactional).
Otherwise, fetch size is ignore and postgresql just pulls in the entire select.
Thanks
--nick
was:
Could you please give the opportunity to disable autoCommit in order for the JDBC page size to work (even if the store is not transactional).
Otherwise, fetch size is ignore and postgresql just pulls in the entire select.
Thanks
--nick
> JDBCStringBasedStore should disable auto commit for publish methods
> -------------------------------------------------------------------
>
> Key: ISPN-9752
> URL: https://issues.jboss.org/browse/ISPN-9752
> Project: Infinispan
> Issue Type: Bug
> Reporter: Nicolas Ocquidant
> Priority: Major
>
> Some JDBC drivers do not do paging for result sets when auto commit is disabled, namely postgresql
> https://jdbc.postgresql.org/documentation/83/query.html#query-with-cursor
> There shouldn't be any drawbacks of disabling auto commit before performing the query. We wouldn't even need to rollback/commit the connection and just return it to the pool. The pool can do that for us as we don't care if it is committed as it is a read only query.
> Could you please give the opportunity to disable autoCommit in order for the JDBC page size to work (even if the store is not transactional).
> Otherwise, fetch size is ignore and postgresql just pulls in the entire select.
> Thanks
> --nick
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9752) Disable autoCommit
by Nicolas Ocquidant (Jira)
Nicolas Ocquidant created ISPN-9752:
---------------------------------------
Summary: Disable autoCommit
Key: ISPN-9752
URL: https://issues.jboss.org/browse/ISPN-9752
Project: Infinispan
Issue Type: Bug
Reporter: Nicolas Ocquidant
Could you please give the opportunity to disable autoCommit in order for the JDBC page size to work (even if the store is not transactional).
Otherwise, fetch size is ignore and postgresql just pulls in the entire select.
Thanks
--nick
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months