[JBoss JIRA] (ISPN-8551) JdbcStringBasedStore SQL Server upsert locks on data not key
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8551?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-8551:
-------------------------------
Fix Version/s: 9.2.0.Beta2
9.1.4.Final
> JdbcStringBasedStore SQL Server upsert locks on data not key
> ------------------------------------------------------------
>
> Key: ISPN-8551
> URL: https://issues.jboss.org/browse/ISPN-8551
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.2.0.Alpha2, 9.1.3.Final
> Reporter: Ryan Emerson
> Fix For: 9.2.0.Beta2, 9.1.4.Final
>
>
> The below code applies ON function to the data column, it should be the key column
> {code:java}
> upsertRowSql = String.format("MERGE %1$s WITH (TABLOCK) " +
> "USING (VALUES (?, ?, ?)) AS tmp (%2$s, %3$s, %4$s) " +
> "ON (%1$s.%2$s = tmp.%2$s) " +
> "WHEN MATCHED THEN UPDATE SET %3$s = tmp.%3$s, %4$s = tmp.%4$s " +
> "WHEN NOT MATCHED THEN INSERT (%2$s, %3$s, %4$s) VALUES (tmp.%2$s, tmp.%3$s, tmp.%4$s);",
> getTableName(), config.dataColumnName(), config.timestampColumnName(), config.idColumnName());
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (ISPN-8551) JdbcStringBasedStore SQL Server upsert locks on data not key
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8551?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-8551.
--------------------------------
Resolution: Done
> JdbcStringBasedStore SQL Server upsert locks on data not key
> ------------------------------------------------------------
>
> Key: ISPN-8551
> URL: https://issues.jboss.org/browse/ISPN-8551
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.2.0.Alpha2, 9.1.3.Final
> Reporter: Ryan Emerson
> Fix For: 9.2.0.Beta2, 9.1.4.Final
>
>
> The below code applies ON function to the data column, it should be the key column
> {code:java}
> upsertRowSql = String.format("MERGE %1$s WITH (TABLOCK) " +
> "USING (VALUES (?, ?, ?)) AS tmp (%2$s, %3$s, %4$s) " +
> "ON (%1$s.%2$s = tmp.%2$s) " +
> "WHEN MATCHED THEN UPDATE SET %3$s = tmp.%3$s, %4$s = tmp.%4$s " +
> "WHEN NOT MATCHED THEN INSERT (%2$s, %3$s, %4$s) VALUES (tmp.%2$s, tmp.%3$s, tmp.%4$s);",
> getTableName(), config.dataColumnName(), config.timestampColumnName(), config.idColumnName());
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (ISPN-8551) JdbcStringBasedStore SQL Server upsert locks on data not key
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8551?page=com.atlassian.jira.plugin.... ]
Ryan Emerson reassigned ISPN-8551:
----------------------------------
Assignee: (was: Ryan Emerson)
> JdbcStringBasedStore SQL Server upsert locks on data not key
> ------------------------------------------------------------
>
> Key: ISPN-8551
> URL: https://issues.jboss.org/browse/ISPN-8551
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.2.0.Alpha2, 9.1.3.Final
> Reporter: Ryan Emerson
>
> The below code applies ON function to the data column, it should be the key column
> {code:java}
> upsertRowSql = String.format("MERGE %1$s WITH (TABLOCK) " +
> "USING (VALUES (?, ?, ?)) AS tmp (%2$s, %3$s, %4$s) " +
> "ON (%1$s.%2$s = tmp.%2$s) " +
> "WHEN MATCHED THEN UPDATE SET %3$s = tmp.%3$s, %4$s = tmp.%4$s " +
> "WHEN NOT MATCHED THEN INSERT (%2$s, %3$s, %4$s) VALUES (tmp.%2$s, tmp.%3$s, tmp.%4$s);",
> getTableName(), config.dataColumnName(), config.timestampColumnName(), config.idColumnName());
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (ISPN-8551) JdbcStringBasedStore SQL Server upsert locks on data not key
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8551?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-8551:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5597
> JdbcStringBasedStore SQL Server upsert locks on data not key
> ------------------------------------------------------------
>
> Key: ISPN-8551
> URL: https://issues.jboss.org/browse/ISPN-8551
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.2.0.Alpha2, 9.1.3.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
>
> The below code applies ON function to the data column, it should be the key column
> {code:java}
> upsertRowSql = String.format("MERGE %1$s WITH (TABLOCK) " +
> "USING (VALUES (?, ?, ?)) AS tmp (%2$s, %3$s, %4$s) " +
> "ON (%1$s.%2$s = tmp.%2$s) " +
> "WHEN MATCHED THEN UPDATE SET %3$s = tmp.%3$s, %4$s = tmp.%4$s " +
> "WHEN NOT MATCHED THEN INSERT (%2$s, %3$s, %4$s) VALUES (tmp.%2$s, tmp.%3$s, tmp.%4$s);",
> getTableName(), config.dataColumnName(), config.timestampColumnName(), config.idColumnName());
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (ISPN-8551) JdbcStringBasedStore SQL Server upsert locks on data not key
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-8551?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-8551:
-------------------------------
Status: Open (was: New)
> JdbcStringBasedStore SQL Server upsert locks on data not key
> ------------------------------------------------------------
>
> Key: ISPN-8551
> URL: https://issues.jboss.org/browse/ISPN-8551
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 9.2.0.Alpha2, 9.1.3.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
>
> The below code applies ON function to the data column, it should be the key column
> {code:java}
> upsertRowSql = String.format("MERGE %1$s WITH (TABLOCK) " +
> "USING (VALUES (?, ?, ?)) AS tmp (%2$s, %3$s, %4$s) " +
> "ON (%1$s.%2$s = tmp.%2$s) " +
> "WHEN MATCHED THEN UPDATE SET %3$s = tmp.%3$s, %4$s = tmp.%4$s " +
> "WHEN NOT MATCHED THEN INSERT (%2$s, %3$s, %4$s) VALUES (tmp.%2$s, tmp.%3$s, tmp.%4$s);",
> getTableName(), config.dataColumnName(), config.timestampColumnName(), config.idColumnName());
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (ISPN-8281) Overload collect() to take Supplier and SerializableSupplier
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-8281?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-8281:
-----------------------------------
Fix Version/s: 9.2.0.Alpha2
> Overload collect() to take Supplier and SerializableSupplier
> ------------------------------------------------------------
>
> Key: ISPN-8281
> URL: https://issues.jboss.org/browse/ISPN-8281
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 9.2.0.Alpha2, 9.2.0.Final
>
>
> Whenever a collect() is called in a distributed environment, you have to wrap up in a serializable supplier method call to make it serializable, e.g.
> {code}
> Map<Integer, Long> totalPerHour = cache.values().stream()
> .collect(
> CacheCollectors.serializableCollector(() -> Collectors.groupingBy(
> e -> getHourOfDay(e.departureTs),
> Collectors.counting()
> )));
> {code}
> This is a bit clunky. We should overload collect to take a SerializableSupplier in CacheStream.
> It would also be nice to have an overloaded version that takes Supplier in case you want to provide your own serialization for it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (ISPN-6395) Unify clustered queries with non clustered queries
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6395?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6395:
------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/5600
> Unify clustered queries with non clustered queries
> --------------------------------------------------
>
> Key: ISPN-6395
> URL: https://issues.jboss.org/browse/ISPN-6395
> Project: Infinispan
> Issue Type: Feature Request
> Components: Embedded Querying
> Affects Versions: 9.2.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 9.2.0.Final
>
>
> Clustered queries currently have a different API, and they work on top on non-shared indexes.
> We should detect (or make it explicitly configurable) the fact that the index is not shared and use clustered query internally, but exposing a single Query interface.
> We should also expose a new parameter in the Query API to allow doing a query in a single step or two steps (broadcast).
> Last, but not least, we should offer the possibility to broadcast Ickle queries apart from LuceneQueries
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (ISPN-6395) Unify clustered queries with non clustered queries
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6395?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6395:
------------------------------------
Affects Version/s: 9.2.0.Beta1
> Unify clustered queries with non clustered queries
> --------------------------------------------------
>
> Key: ISPN-6395
> URL: https://issues.jboss.org/browse/ISPN-6395
> Project: Infinispan
> Issue Type: Feature Request
> Components: Embedded Querying
> Affects Versions: 9.2.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 9.2.0.Final
>
>
> Clustered queries currently have a different API, and they work on top on non-shared indexes.
> We should detect (or make it explicitly configurable) the fact that the index is not shared and use clustered query internally, but exposing a single Query interface.
> We should also expose a new parameter in the Query API to allow doing a query in a single step or two steps (broadcast).
> Last, but not least, we should offer the possibility to broadcast Ickle queries apart from LuceneQueries
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (ISPN-6395) Unify clustered queries with non clustered queries
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6395?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-6395:
------------------------------------
Fix Version/s: 9.2.0.Final
> Unify clustered queries with non clustered queries
> --------------------------------------------------
>
> Key: ISPN-6395
> URL: https://issues.jboss.org/browse/ISPN-6395
> Project: Infinispan
> Issue Type: Feature Request
> Components: Embedded Querying
> Affects Versions: 9.2.0.Beta1
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Fix For: 9.2.0.Final
>
>
> Clustered queries currently have a different API, and they work on top on non-shared indexes.
> We should detect (or make it explicitly configurable) the fact that the index is not shared and use clustered query internally, but exposing a single Query interface.
> We should also expose a new parameter in the Query API to allow doing a query in a single step or two steps (broadcast).
> Last, but not least, we should offer the possibility to broadcast Ickle queries apart from LuceneQueries
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month