[JBoss JIRA] (ISPN-5414) Support (named) parameters in DSL based queries
by Prashant Thakur (JIRA)
[ https://issues.jboss.org/browse/ISPN-5414?page=com.atlassian.jira.plugin.... ]
Prashant Thakur commented on ISPN-5414:
---------------------------------------
Hi Adrain,
A quick query on the scope of this implementation.
Will we be avoiding parsing with this implementation. Will the parsed results be stored in query cache and named parameters be applied . We are working on similar modification and we can share our thoughts and design if its solving above two issues
> Support (named) parameters in DSL based queries
> -----------------------------------------------
>
> Key: ISPN-5414
> URL: https://issues.jboss.org/browse/ISPN-5414
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Querying
> Affects Versions: 8.0.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.0.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (ISPN-5596) "Cannot clear data directory" in SoftIndexFileStore when clear() is called after stopping and restarting cache
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-5596?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-5596:
-----------------------------------
Could you then set logging on org.infinispan.persistence to TRACE and attach the log here? Btw., attaching is the recommended way for test-cases too, rather than pasting the code directly.
I think that it may be related to the fact that Windows does not allow you a file that is currently open, but it will be easier to check that with logs rather than guess.
> "Cannot clear data directory" in SoftIndexFileStore when clear() is called after stopping and restarting cache
> --------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-5596
> URL: https://issues.jboss.org/browse/ISPN-5596
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 7.2.3.Final
> Environment: Windows 7
> Reporter: Andreas Pabst
> Assignee: Radim Vansa
>
> When stopping and restarting a cache with SoftIndexFileStore persistence, it behaves strangely.
> Calling cache.clear() leads to the following exception:
> ERROR: ISPN000136: Execution error
> org.infinispan.persistence.spi.PersistenceException: Cannot clear data directory!
> at org.infinispan.persistence.sifs.SoftIndexFileStore.clear(SoftIndexFileStore.java:234)
> at org.infinispan.persistence.manager.PersistenceManagerImpl.clearAllStores(PersistenceManagerImpl.java:372)
> at org.infinispan.interceptors.CacheWriterInterceptor.visitClearCommand(CacheWriterInterceptor.java:158)
> ...
> Caused by: java.io.IOException: Cannot delete file soft-index-test\data\2
> at org.infinispan.persistence.sifs.FileProvider.clear(FileProvider.java:205)
> at org.infinispan.persistence.sifs.SoftIndexFileStore.clear(SoftIndexFileStore.java:232)
> If the manager is also stopped and recreated every time, this only happens after the third iteration.
> Calling cache.remove() in the same place leads to an unrecoverable corruption of the cache store files: java.lang.IllegalArgumentException: Negative position
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (ISPN-5661) There are a number of broken links in the docs that contain {infinispanversion}
by Alan Field (JIRA)
Alan Field created ISPN-5661:
--------------------------------
Summary: There are a number of broken links in the docs that contain {infinispanversion}
Key: ISPN-5661
URL: https://issues.jboss.org/browse/ISPN-5661
Project: Infinispan
Issue Type: Bug
Components: Documentation-Core
Affects Versions: 8.0.0.Beta2
Reporter: Alan Field
I initially found an instance of the text {infinispanversion} in the properties file configuration example of section 13.4.3. Java Hot Rod client. However, if you search for that string, there are a number of links to the API docs that are not rendered as links and contain that text.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months
[JBoss JIRA] (ISPN-5558) DistributedTaskPart.equals() implementation is wrong
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5558?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5558:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1250033|https://bugzilla.redhat.com/show_bug.cgi?id=1250033] from POST to MODIFIED
> DistributedTaskPart.equals() implementation is wrong
> ----------------------------------------------------
>
> Key: ISPN-5558
> URL: https://issues.jboss.org/browse/ISPN-5558
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Distributed Execution and Map/Reduce
> Affects Versions: 7.2.2.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 8.0.0.Beta1, 7.2.4.Final, 8.0.0.Final
>
>
> {{DistributedExecutorService.submitEverywhere()}} returns a list of futures, one future for each targeted node. Because of how {{DistributedTaskPart.equals()}} is implemented, all the futures in the list appear to be equal, even though their target node is different and their result will also be different.
> The simplest fix would be to remove the equals() and hashCode() overloads from {{DistributedTaskPart}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 9 months