November 2016 - infinispan-issues

[JBoss JIRA] (ISPN-7205) Query DSL should not require the use of toBuilder() method to switch context

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7205?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7205: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Query DSL should not require the use of toBuilder() method to switch context > ---------------------------------------------------------------------------- > > Key: ISPN-7205 > URL: https://issues.jboss.org/browse/ISPN-7205 > Project: Infinispan > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > After completing a 'having' filter condition we need to call toBuilder() in order to move from FilterConditionContext to QueryBuilder context to be able to finalize the constuction and invoke build(). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2826) CacheQuery.list() returns List<Object>, which is hard to cast

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-2826?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-2826: ------------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > CacheQuery.list() returns List<Object>, which is hard to cast > ------------------------------------------------------------- > > Key: ISPN-2826 > URL: https://issues.jboss.org/browse/ISPN-2826 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Ray Tsang > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > In example for Books in https://docs.jboss.org/author/display/ISPN/Querying+Infinispan > ~~ snip snip ~~ > CacheQuery query = searchManager.getQuery(luceneQuery, Book.class); > // and there are your results! > List<Book> objectList = query.list(); > ~~ snip snip ~~ > This doesn't actually work. CacheQuery.list() returns List<Object> > Thus, you will need to cast: List<Book> books = (List<Book>) cq.list(); > But this wouldn't work... Instead you'll end up doing: List<Book> books = (List<Book>)(List<?>) cq.list(); -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5467) Design new interceptor interfaces for sequential invocation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5467?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5467: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Design new interceptor interfaces for sequential invocation > ----------------------------------------------------------- > > Key: ISPN-5467 > URL: https://issues.jboss.org/browse/ISPN-5467 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 7.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Beta1, 9.0.0.Final > > > We need the interceptors to execute in sequence instead of using a stack in order to allow interrupting the execution of a command on one thread and continuing the execution on another thread. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7209) Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-7209?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-7209: ---------------------------------- Assignee: Ryan Emerson > Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-7209 > URL: https://issues.jboss.org/browse/ISPN-7209 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha4 > Reporter: Jiří Holuša > Assignee: Ryan Emerson > > Given following scenario: > 1) store entry to ISPN server via Hot Rod (e.g. with RemoteCache) > 2) have the server configured to use JdbcStringBasedStore > 3) used database is MariaDB 10 > Following exception is thrown: > {code} > ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (HotRodServerHandler-3-2) ISPN008024: Error while storing string key to database; key: '9A09AJAAAAAAAAA==': java.sql.BatchUpdateException: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' > {code} > Note that his doesn't happen when stored via, for example, Memcached client. Also this issue doesn't appear in library mode, doesn't appear in any with any other database (including MySQL, which is very similar to MariaDB). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3618) Cannot retrieve evicted entries from Microsoft SQL Server 2012/2008R2

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-3618?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-3618: ---------------------------------- Assignee: Ryan Emerson (was: Ion Savin) > Cannot retrieve evicted entries from Microsoft SQL Server 2012/2008R2 > --------------------------------------------------------------------- > > Key: ISPN-3618 > URL: https://issues.jboss.org/browse/ISPN-3618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Affects Versions: 6.0.0.CR1 > Reporter: Jakub Markos > Assignee: Ryan Emerson > Attachments: server_mssql2012_mysql55.log.zip > > > When using this configuration: > {code:xml} > <local-cache name="default" start="EAGER" batching="false"> > <locking isolation="READ_COMMITTED" acquire-timeout="20000" concurrency-level="500" striping="false" /> > <transaction mode="NONE" /> > <eviction strategy="LRU" max-entries="2"/> > <string-keyed-jdbc-store name="defaultStoreName" datasource="java:jboss/datasources/JdbcDS" passivation="false" preload="true" purge="false"> > <string-keyed-table prefix="EDG_STRING"> > <id-column name="id" type="VARCHAR(255)"/> > <data-column name="datum" type="VARBINARY(1000)"/> > <timestamp-column name="version" type="BIGINT"/> > </string-keyed-table> > </string-keyed-jdbc-store> > </local-cache> > {code} > and running this code: > {code} > RemoteCache<Object, Object> cache = new RemoteCacheManager(conf).getCache(); > cache.clear(); > cache.put(new Double(10), new Double(10)); > cache.put(new Double(20), new Double(20)); > cache.put(new Double(30), new Double(30)); // key 10 is evicted > System.out.println(cache.get(new Double(10))); > System.out.println(cache.get(new Double(20))); > System.out.println(cache.get(new Double(30))); > {code} > output: > {quote} > null > 20.0 > 30.0 > {quote} > Attached are logs for mssql2012 and mysql55 (where it works). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6742) Console shows cache available and disabled at the same time

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6742?page=com.atlassian.jira.plugin.... ] Roman Macor reopened ISPN-6742: ------------------------------- I can still reproduce this, the screen-shot is still valid. > Console shows cache available and disabled at the same time > ----------------------------------------------------------- > > Key: ISPN-6742 > URL: https://issues.jboss.org/browse/ISPN-6742 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Alpha3 > > Attachments: attachment.png > > > Page: go to cache detail and click "Actions" -> "Disable". > After confirmation, the cache status is still "Available", but new red box appears with text "Disabled", see the attachment. This doesn't seem to me very intuitive, if the cache is disabled, it should be IMO unavailable and this should be also reflected in the caches list. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7203) Administration console - number of entries is not displayed in node view

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7203?page=com.atlassian.jira.plugin.... ] Roman Macor resolved ISPN-7203. ------------------------------- Resolution: Done [~vblagojevic] you are right, this doesn't happen with a clean server, it might have been in an inconsistent state. I'm closing the issue, I will try to investigate when exactly this happens and I will reopen this issue if it turns out to be a bug after all. Thanks, Vladimir! > Administration console - number of entries is not displayed in node view > ------------------------------------------------------------------------ > > Key: ISPN-7203 > URL: https://issues.jboss.org/browse/ISPN-7203 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > Steps to reproduce: > Click on clusters tab -> click on cluster -> click on node > Result: IP: 127.0.0.1 - entries > Expected result: number of entries should be e.g. shown: IP: 127.0.0.1 - 10 entries -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7209) Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB

by Jiří Holuša (JIRA)

[ https://issues.jboss.org/browse/ISPN-7209?page=com.atlassian.jira.plugin.... ] Jiří Holuša updated ISPN-7209: ------------------------------ Summary: Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB (was: Collation not set properly data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB) > Collation not set properly when data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-7209 > URL: https://issues.jboss.org/browse/ISPN-7209 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Alpha4 > Reporter: Jiří Holuša > > Given following scenario: > 1) store entry to ISPN server via Hot Rod (e.g. with RemoteCache) > 2) have the server configured to use JdbcStringBasedStore > 3) used database is MariaDB 10 > Following exception is thrown: > {code} > ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (HotRodServerHandler-3-2) ISPN008024: Error while storing string key to database; key: '9A09AJAAAAAAAAA==': java.sql.BatchUpdateException: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' > {code} > Note that his doesn't happen when stored via, for example, Memcached client. Also this issue doesn't appear in library mode, doesn't appear in any with any other database (including MySQL, which is very similar to MariaDB). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7209) Collation not set properly data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB

by Jiří Holuša (JIRA)

Jiří Holuša created ISPN-7209: --------------------------------- Summary: Collation not set properly data stored via Hot Rod when JdbcStringBasedStore is used with MariaDB Key: ISPN-7209 URL: https://issues.jboss.org/browse/ISPN-7209 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 9.0.0.Alpha4 Reporter: Jiří Holuša Given following scenario: 1) store entry to ISPN server via Hot Rod (e.g. with RemoteCache) 2) have the server configured to use JdbcStringBasedStore 3) used database is MariaDB 10 Following exception is thrown: {code} ERROR [org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore] (HotRodServerHandler-3-2) ISPN008024: Error while storing string key to database; key: '9A09AJAAAAAAAAA==': java.sql.BatchUpdateException: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' {code} Note that his doesn't happen when stored via, for example, Memcached client. Also this issue doesn't appear in library mode, doesn't appear in any with any other database (including MySQL, which is very similar to MariaDB). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7208) Allow specifying JNDI when using Spring integration

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7208: ----------------------------------------- Summary: Allow specifying JNDI when using Spring integration Key: ISPN-7208 URL: https://issues.jboss.org/browse/ISPN-7208 Project: Infinispan Issue Type: Feature Request Components: Spring Integration Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Priority: Minor Currently it is not possible to use {{CacheManager}} instances deployed on WildFly in a convenient way. The easiest trick would be to use JNDI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2016