[JBoss JIRA] (ISPN-9752) JDBCStringBasedStore should disable auto commit for publish methods
by Ryan Emerson (Jira)
[ https://issues.jboss.org/browse/ISPN-9752?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-9752.
--------------------------------
Fix Version/s: 10.0.0.Alpha2
9.4.3.Final
Assignee: William Burns
Resolution: Done
> 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
> Assignee: William Burns
> Priority: Major
> Fix For: 10.0.0.Alpha2, 9.4.3.Final
>
>
> Some JDBC drivers do not do paging for result sets when auto commit is enabled, 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-9756) Improve ETag generation in the REST server
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-9756?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9756:
------------------------------------
Affects Version/s: 9.4.2.Final
> Improve ETag generation in the REST server
> ------------------------------------------
>
> Key: ISPN-9756
> URL: https://issues.jboss.org/browse/ISPN-9756
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST
> Affects Versions: 9.4.2.Final, 10.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Etags, used to support conditional operations on REST are calculated using MurmurHash3 and it is not stored in the metadata but rather calculated on the fly.
> A better solution would be to use the in-place version generator similar to Hot Rod (numeric version)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9756) Improve ETag generation in the REST server
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-9756?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-9756:
------------------------------------
Description:
Etags, used to support conditional operations on REST are calculated using MurmurHash3 and it is not stored in the metadata but rather calculated on the fly.
A better solution would be to reuse the in-place version generator of Hot Rod (numeric version)
was:
Etags, used to support conditional operations on REST are calculated using MurmurHash3 and it is not stored in the metadata but rather calculated on the fly.
A better solution would be to use the in-place version generator similar to Hot Rod (numeric version)
> Improve ETag generation in the REST server
> ------------------------------------------
>
> Key: ISPN-9756
> URL: https://issues.jboss.org/browse/ISPN-9756
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST
> Affects Versions: 9.4.2.Final, 10.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Etags, used to support conditional operations on REST are calculated using MurmurHash3 and it is not stored in the metadata but rather calculated on the fly.
> A better solution would be to reuse the in-place version generator of Hot Rod (numeric version)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9756) Improve ETag generation in the REST server
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-9756:
---------------------------------------
Summary: Improve ETag generation in the REST server
Key: ISPN-9756
URL: https://issues.jboss.org/browse/ISPN-9756
Project: Infinispan
Issue Type: Enhancement
Components: REST
Affects Versions: 10.0.0.Alpha1
Reporter: Gustavo Fernandes
Etags, used to support conditional operations on REST are calculated using MurmurHash3 and it is not stored in the metadata but rather calculated on the fly.
A better solution would be to use the in-place version generator similar to Hot Rod (numeric version)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9756) Improve ETag generation in the REST server
by Gustavo Fernandes (Jira)
[ https://issues.jboss.org/browse/ISPN-9756?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes reassigned ISPN-9756:
---------------------------------------
Assignee: Gustavo Fernandes
> Improve ETag generation in the REST server
> ------------------------------------------
>
> Key: ISPN-9756
> URL: https://issues.jboss.org/browse/ISPN-9756
> Project: Infinispan
> Issue Type: Enhancement
> Components: REST
> Affects Versions: 10.0.0.Alpha1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Etags, used to support conditional operations on REST are calculated using MurmurHash3 and it is not stored in the metadata but rather calculated on the fly.
> A better solution would be to use the in-place version generator similar to Hot Rod (numeric version)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9755) Version dropdown doesn't work in the server guide
by Dan Berindei (Jira)
Dan Berindei created ISPN-9755:
----------------------------------
Summary: Version dropdown doesn't work in the server guide
Key: ISPN-9755
URL: https://issues.jboss.org/browse/ISPN-9755
Project: Infinispan
Issue Type: Bug
Components: Website
Affects Versions: 10.0.0.Alpha1, 9.4.2.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 10.0.0.Beta1, 9.4.3.Final
While testing the release I noticed that the version dropdown from the server guide redirects to the user guide.
I also noticed that the {{infinispanversion}} placeholder is not replaced in the js source, so the current version is not selected in the dropdown.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9755) Version dropdown doesn't work in the server guide
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9755?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9755:
-------------------------------
Status: Open (was: New)
> Version dropdown doesn't work in the server guide
> -------------------------------------------------
>
> Key: ISPN-9755
> URL: https://issues.jboss.org/browse/ISPN-9755
> Project: Infinispan
> Issue Type: Bug
> Components: Website
> Affects Versions: 9.4.2.Final, 10.0.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Fix For: 10.0.0.Beta1, 9.4.3.Final
>
>
> While testing the release I noticed that the version dropdown from the server guide redirects to the user guide.
> I also noticed that the {{infinispanversion}} placeholder is not replaced in the js source, so the current version is not selected in the dropdown.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months