[JBoss JIRA] (ISPN-9726) Document max clause property on boolean query
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9726?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9726:
----------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1 (was: Sprint 10.0.0.Alpha1)
> Document max clause property on boolean query
> ---------------------------------------------
>
> Key: ISPN-9726
> URL: https://issues.jboss.org/browse/ISPN-9726
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying, Remote Querying
> Affects Versions: 10.0.0.Alpha1
> Reporter: Katia Aresti
> Assignee: Adrian Nistor
> Priority: Major
> Fix For: 9.4.2.Final, 10.0.0.Alpha1
>
>
> Document the ability to override org.apache.lucene.search.BooleanQuery.maxClauseCount using infinispan.query.lucene.max-boolean-clauses JVM system property.
--
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 Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9745?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9745:
----------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1 (was: Sprint 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: 9.4.2.Final, 10.0.0.Alpha1
>
>
> 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-9693) Make MarshalledEntryImpl private and utilise MarshalledEntryFactory instead
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9693?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9693:
----------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1 (was: Sprint 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.Alpha1
>
>
> 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-9679) Move property replacement in parser to XMLStreamReader
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9679?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9679:
----------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1 (was: Sprint 10.0.0.Alpha1)
> Move property replacement in parser to XMLStreamReader
> ------------------------------------------------------
>
> Key: ISPN-9679
> URL: https://issues.jboss.org/browse/ISPN-9679
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Alpha1
>
>
> The property replacement is performed "manually" within the parsers. It would be better if it were done by the XMLStreamReader implementation so that we can also supply custom properties programmatically without relying on the system properties (testability)
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-9667) DefaultCacheManager inconsistent status checks
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9667?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9667:
----------------------------------
Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1 (was: Sprint 10.0.0.Alpha1)
> DefaultCacheManager inconsistent status checks
> ----------------------------------------------
>
> Key: ISPN-9667
> URL: https://issues.jboss.org/browse/ISPN-9667
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 9.4.2.Final, 10.0.0.Alpha1
>
>
> {{DefaultCacheManager.getTransport()}} returns {{null}} when the manager is stopping, it should not.
> To make things worse, {{DefaultCacheManager.getStatus()}} returns the status of the {{GlobalComponentRegistry}}, which is still {{RUNNING}} while caches are shutting down. That means {{DCM.getTransport()}} and {{DCM.getAddress()}} return {{null}} while the cache are stopping, and breaks distributed streams on caches that are still running.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-8234) Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8234?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8234:
----------------------------------
Sprint: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1, Sprint 9.4.0.Final (was: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 9.4.0.Final)
> Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema
> ------------------------------------------------------------------------------
>
> Key: ISPN-8234
> URL: https://issues.jboss.org/browse/ISPN-8234
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Querying
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Priority: Major
>
> These annotations must behave identically to their Hibernate Search counterparts defined in org.hibernate.search.annotations package.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months
[JBoss JIRA] (ISPN-2445) Safe shutdown - transfer data to other nodes
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-2445?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-2445:
----------------------------------
Sprint: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Beta1 (was: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1)
> Safe shutdown - transfer data to other nodes
> --------------------------------------------
>
> Key: ISPN-2445
> URL: https://issues.jboss.org/browse/ISPN-2445
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Matej Lazar
> Assignee: Dan Berindei
> Priority: Major
>
> Distributed cache should provide an configuration option to block shutdown until data from shutting down node is transferred to other nodes.
> This feature is useful if Infinispan is used as persistent storage.
> Without this option, in a cloud environment, where server node is deleted on scale down event, users are forced to use external storage, if they don't want to loose data.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 4 months