July 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8061) Upgrade to Hibernate Search 5.8.0.Beta4 : SPI cleanup

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-8061?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-8061: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5286 > Upgrade to Hibernate Search 5.8.0.Beta4 : SPI cleanup > ----------------------------------------------------- > > Key: ISPN-8061 > URL: https://issues.jboss.org/browse/ISPN-8061 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.1.0.Final > > > This upgrade of Hibernate Search is very minor in terms of functionality, but represents an important milestone towards using the new SPI. > Many of the deprecated methods used by Infinispan in the past have been removed, so I will recommend to upgrade to maintain compatibility with further releases of this generation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8061) Upgrade to Hibernate Search 5.8.0.Beta4 : SPI cleanup

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-8061: ------------------------------------- Summary: Upgrade to Hibernate Search 5.8.0.Beta4 : SPI cleanup Key: ISPN-8061 URL: https://issues.jboss.org/browse/ISPN-8061 Project: Infinispan Issue Type: Component Upgrade Components: Embedded Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 9.1.0.Final This upgrade of Hibernate Search is very minor in terms of functionality, but represents an important milestone towards using the new SPI. Many of the deprecated methods used by Infinispan in the past have been removed, so I will recommend to upgrade to maintain compatibility with further releases of this generation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8061) Upgrade to Hibernate Search 5.8.0.Beta4 : SPI cleanup

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-8061?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-8061: ---------------------------------- Status: Open (was: New) > Upgrade to Hibernate Search 5.8.0.Beta4 : SPI cleanup > ----------------------------------------------------- > > Key: ISPN-8061 > URL: https://issues.jboss.org/browse/ISPN-8061 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.1.0.Final > > > This upgrade of Hibernate Search is very minor in terms of functionality, but represents an important milestone towards using the new SPI. > Many of the deprecated methods used by Infinispan in the past have been removed, so I will recommend to upgrade to maintain compatibility with further releases of this generation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7973) Investigate Service Brokers

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-7973: ------------------------------------------- OpenShift manual for this: https://docs.openshift.org/latest/dev_guide/templates.html#writing-exposi... > Investigate Service Brokers > --------------------------- > > Key: ISPN-7973 > URL: https://issues.jboss.org/browse/ISPN-7973 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8060) Remove indexed entity autodetection

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-8060: ----------------------------------- Summary: Remove indexed entity autodetection Key: ISPN-8060 URL: https://issues.jboss.org/browse/ISPN-8060 Project: Infinispan Issue Type: Enhancement Components: Embedded Querying, Remote Querying Reporter: Adrian Nistor Fix For: 10.0.0.Final All indexed types should be predeclared. Existing tests for autodetection should be converted into tests that prove autodetection is no longer supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8060) Remove indexed entity autodetection

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8060?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-8060: -------------------------------- Status: Open (was: New) > Remove indexed entity autodetection > ----------------------------------- > > Key: ISPN-8060 > URL: https://issues.jboss.org/browse/ISPN-8060 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Fix For: 10.0.0.Final > > > All indexed types should be predeclared. > Existing tests for autodetection should be converted into tests that prove autodetection is no longer supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8060) Remove indexed entity autodetection

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-8060?page=com.atlassian.jira.plugin.... ] Adrian Nistor reassigned ISPN-8060: ----------------------------------- Assignee: Adrian Nistor > Remove indexed entity autodetection > ----------------------------------- > > Key: ISPN-8060 > URL: https://issues.jboss.org/browse/ISPN-8060 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 10.0.0.Final > > > All indexed types should be predeclared. > Existing tests for autodetection should be converted into tests that prove autodetection is no longer supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7827) Additional Documentation for Cluster Executor

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7827?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7827: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Additional Documentation for Cluster Executor > --------------------------------------------- > > Key: ISPN-7827 > URL: https://issues.jboss.org/browse/ISPN-7827 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: William Burns > Assignee: William Burns > Fix For: 9.1.0.Final > > > Cluster Executor has some additional API changes. We need to document these in the user guide. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7973) Investigate Service Brokers

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-7973 at 7/12/17 9:17 AM: -------------------------------------------------------------------- Things to clarify and other issues: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). * Shall we create separate separate service or one service with multiple plans? * It seems there is no way to let the client specify how the secret created by binding should look like. It can be defined from a service broker perspective (have a look at this [test|https://github.com/openshift/origin/blob/f4b675ea183f1ebec3d15373337...]). So it might be better (for now?) to let the template create a secret for Service Consumers. * In addition to previous point - it seems that [MariaDB Template|https://github.com/openshift/origin/blob/master/examples/db-temp...] handles this correctly. We should copy its behavior. was (Author: sebastian.laskawiec): Things to clarify and other issues: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). * Shall we create separate separate service or one service with multiple plans? * It seems there is no way to let the client specify how the secret created by binding should look like. It can be defined from a service broker perspective (have a look at this [test|https://github.com/openshift/origin/blob/f4b675ea183f1ebec3d15373337...]). So it might be better (for now?) to let the template create a secret for Service Consumers. > Investigate Service Brokers > --------------------------- > > Key: ISPN-7973 > URL: https://issues.jboss.org/browse/ISPN-7973 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7973) Investigate Service Brokers

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7973?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-7973 at 7/12/17 8:20 AM: -------------------------------------------------------------------- Things to clarify and other issues: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). * Shall we create separate separate service or one service with multiple plans? * It seems there is no way to let the client specify how the secret created by binding should look like. It can be defined from a service broker perspective (have a look at this [test|https://github.com/openshift/origin/blob/f4b675ea183f1ebec3d15373337...]). So it might be better (for now?) to let the template create a secret for Service Consumers. was (Author: sebastian.laskawiec): Things to clarify and other issues: * No UI for creating/deleting/editing ServicePlans. It is also worth to mention that OpenShift Origin (with {{oc cluster up}}) comes with one default plan (use {{oc edit ServiceClass infinispan-ephemeral}} to view it). * Shall we create separate separate service or one service with multiple plans? > Investigate Service Brokers > --------------------------- > > Key: ISPN-7973 > URL: https://issues.jboss.org/browse/ISPN-7973 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 July 2017