August 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7885) "org.hibernate.search.exception.SearchException: Not a valid ScoreDoc index" under high load

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-7885?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on ISPN-7885: --------------------------------------- Infinispan version {{9.0.1.Final}} depends on Hibernate Search {{5.7.0.Final}, while HSEARCH-2691 was fixed in {{5.7.1.Final}} so we would need this upgrade. > "org.hibernate.search.exception.SearchException: Not a valid ScoreDoc index" under high load > -------------------------------------------------------------------------------------------- > > Key: ISPN-7885 > URL: https://issues.jboss.org/browse/ISPN-7885 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.6.Final, 9.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7885) "org.hibernate.search.exception.SearchException: Not a valid ScoreDoc index" under high load

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-7885?page=com.atlassian.jira.plugin.... ] Sanne Grinovero edited comment on ISPN-7885 at 8/14/17 2:38 PM: ---------------------------------------------------------------- Infinispan version {{9.0.1.Final}} depends on Hibernate Search {{5.7.0.Final}}, while HSEARCH-2691 was fixed in {{5.7.1.Final}} so we would need this upgrade. was (Author: sannegrinovero): Infinispan version {{9.0.1.Final}} depends on Hibernate Search {{5.7.0.Final}, while HSEARCH-2691 was fixed in {{5.7.1.Final}} so we would need this upgrade. > "org.hibernate.search.exception.SearchException: Not a valid ScoreDoc index" under high load > -------------------------------------------------------------------------------------------- > > Key: ISPN-7885 > URL: https://issues.jboss.org/browse/ISPN-7885 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.2.6.Final, 9.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5188) Indexing of JSON values

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5188?page=com.atlassian.jira.plugin.... ] Work on ISPN-5188 started by Gustavo Fernandes. ----------------------------------------------- > Indexing of JSON values > ----------------------- > > Key: ISPN-5188 > URL: https://issues.jboss.org/browse/ISPN-5188 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols, Remote Querying > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > > Introduce a JSON marshaller so that JSON values can be indexed and queried using the ProtoBuf schemas. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7418) Add per-cache key/value type information

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7418?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-7418: --------------------------------------- Assignee: Gustavo Fernandes > Add per-cache key/value type information > ---------------------------------------- > > Key: ISPN-7418 > URL: https://issues.jboss.org/browse/ISPN-7418 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > > This part of the transcoding enhancement is related to the changes required to the core cache code to force the cache to store keys and values of a certain type. > The type information should be defined via a MIME type, and should be configured by the user. > A cache can only have a single key+value type combination. A single cache will not support storing data of different key and/or value types. Amongst other reasons, this is done for space efficiency. > Once a cache can be configured with a specific key and value type, the user should be able to retrieve the value with an alternative MIME type. Behind the scenes, the cache should be able to transform the value from the give type to target type on the fly. > As suggested in the wiki, there should be the possibility for the key/value type to be implicitly determined by the key+value type passed in during the first cache write. The aim of this is to enable remote clients to decide what the key+value type are upon writing to the cache for the first time, and hence avoid cache pre-configuration. > Some transcoders might require additional configuration. The cache needs to be able to be configured with the necessary options to do on the fly transcoding for clients. E.g. schema for protobuf...etc. > An important aspect here is that consistent hashing should not be affected by transcoding. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7418) Add per-cache key/value type information

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7418?page=com.atlassian.jira.plugin.... ] Work on ISPN-7418 started by Gustavo Fernandes. ----------------------------------------------- > Add per-cache key/value type information > ---------------------------------------- > > Key: ISPN-7418 > URL: https://issues.jboss.org/browse/ISPN-7418 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > > This part of the transcoding enhancement is related to the changes required to the core cache code to force the cache to store keys and values of a certain type. > The type information should be defined via a MIME type, and should be configured by the user. > A cache can only have a single key+value type combination. A single cache will not support storing data of different key and/or value types. Amongst other reasons, this is done for space efficiency. > Once a cache can be configured with a specific key and value type, the user should be able to retrieve the value with an alternative MIME type. Behind the scenes, the cache should be able to transform the value from the give type to target type on the fly. > As suggested in the wiki, there should be the possibility for the key/value type to be implicitly determined by the key+value type passed in during the first cache write. The aim of this is to enable remote clients to decide what the key+value type are upon writing to the cache for the first time, and hence avoid cache pre-configuration. > Some transcoders might require additional configuration. The cache needs to be able to be configured with the necessary options to do on the fly transcoding for clients. E.g. schema for protobuf...etc. > An important aspect here is that consistent hashing should not be affected by transcoding. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5188) Indexing of JSON values

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5188?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-5188: --------------------------------------- Assignee: Gustavo Fernandes > Indexing of JSON values > ----------------------- > > Key: ISPN-5188 > URL: https://issues.jboss.org/browse/ISPN-5188 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols, Remote Querying > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > > Introduce a JSON marshaller so that JSON values can be indexed and queried using the ProtoBuf schemas. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7422) REST enhancements for transcoding

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7422?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7422: ------------------------------------ Status: Open (was: New) > REST enhancements for transcoding > --------------------------------- > > Key: ISPN-7422 > URL: https://issues.jboss.org/browse/ISPN-7422 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > > Enhance the REST protocol: > * Cache writes can provide key+value MIME type information. > * Cache reads of values can provide MIME type information to transform data sent to the client on the fly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7422) REST enhancements for transcoding

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7422?page=com.atlassian.jira.plugin.... ] Work on ISPN-7422 started by Gustavo Fernandes. ----------------------------------------------- > REST enhancements for transcoding > --------------------------------- > > Key: ISPN-7422 > URL: https://issues.jboss.org/browse/ISPN-7422 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > > Enhance the REST protocol: > * Cache writes can provide key+value MIME type information. > * Cache reads of values can provide MIME type information to transform data sent to the client on the fly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7418) Add per-cache key/value type information

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7418?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7418: ------------------------------------ Status: Open (was: New) > Add per-cache key/value type information > ---------------------------------------- > > Key: ISPN-7418 > URL: https://issues.jboss.org/browse/ISPN-7418 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > > This part of the transcoding enhancement is related to the changes required to the core cache code to force the cache to store keys and values of a certain type. > The type information should be defined via a MIME type, and should be configured by the user. > A cache can only have a single key+value type combination. A single cache will not support storing data of different key and/or value types. Amongst other reasons, this is done for space efficiency. > Once a cache can be configured with a specific key and value type, the user should be able to retrieve the value with an alternative MIME type. Behind the scenes, the cache should be able to transform the value from the give type to target type on the fly. > As suggested in the wiki, there should be the possibility for the key/value type to be implicitly determined by the key+value type passed in during the first cache write. The aim of this is to enable remote clients to decide what the key+value type are upon writing to the cache for the first time, and hence avoid cache pre-configuration. > Some transcoders might require additional configuration. The cache needs to be able to be configured with the necessary options to do on the fly transcoding for clients. E.g. schema for protobuf...etc. > An important aspect here is that consistent hashing should not be affected by transcoding. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7422) REST enhancements for transcoding

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7422?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-7422: --------------------------------------- Assignee: Gustavo Fernandes > REST enhancements for transcoding > --------------------------------- > > Key: ISPN-7422 > URL: https://issues.jboss.org/browse/ISPN-7422 > Project: Infinispan > Issue Type: Sub-task > Reporter: Galder Zamarreño > Assignee: Gustavo Fernandes > > Enhance the REST protocol: > * Cache writes can provide key+value MIME type information. > * Cache reads of values can provide MIME type information to transform data sent to the client on the fly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2017