[JBoss JIRA] (ISPN-12275) Restore support for @Field(analyzer = ...) and @Field(normalizer = ...)
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12275?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12275:
-----------------------------------
Fix Version/s: 12.0.0.Dev05
(was: 12.0.0.Dev04)
> Restore support for @Field(analyzer = ...) and @Field(normalizer = ...)
> -----------------------------------------------------------------------
>
> Key: ISPN-12275
> URL: https://issues.redhat.com/browse/ISPN-12275
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying
> Reporter: Yoann Rodière
> Priority: Major
> Fix For: 12.0.0.Dev05
>
>
> In Infinispan 11 (Hibernate Search 5.10/5.11), it used to be possible to assign an analyzer or normalizer to a field with the following syntax:
> {code}
> @Field(analyzer = @Analyzer(definition = "myAnalyzer"))
> private String myProperty;
> @Field(analyzer = @Normalizer(definition = "myNormalizer"))
> private String myProperty;
> {code}
> It seems that we made a mistake during the upgrade to Search 6, and support for this syntax was removed. All that's left is the property-scoped syntax, where the analyzer is defined next to the field:
> {code}
> @Field
> @Analyzer(definition = "myAnalyzer")
> private String myProperty;
> {code}
> If we want to provide at least partial backward compatibility in annotations, we should restore support for the former syntax (and keep the latter).
> For the record, analyzer assigned using the former syntax take precedence over analyzers assigned using the latter.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12261) Protocol server transport management
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12261?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12261:
-----------------------------------
Fix Version/s: 12.0.0.Dev05
(was: 12.0.0.Dev04)
> Protocol server transport management
> -------------------------------------
>
> Key: ISPN-12261
> URL: https://issues.redhat.com/browse/ISPN-12261
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, JMX, reporting and management, Server
> Affects Versions: 12.0.0.Dev02
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 12.0.0.Dev05
>
>
> the WF-server had the ability to stop/start a transport via the CLI (ISPN-11240).
> The new server should have a similar capability.
> Aside from start/stop, we should also leverage netty's ipfilter handler which allows filtering based on subnet so that traffic can be blocked selectively.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12151) Add error count metric
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12151?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12151:
-----------------------------------
Fix Version/s: 12.0.0.Dev05
(was: 12.0.0.Dev04)
> Add error count metric
> ----------------------
>
> Key: ISPN-12151
> URL: https://issues.redhat.com/browse/ISPN-12151
> Project: Infinispan
> Issue Type: Feature Request
> Components: Analytics
> Affects Versions: 11.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final, 12.0.0.Dev05
>
>
> {{CacheMgmtInterceptor}} has metrics for the different kind of key operations, but errors are not tracked. We should add a metric to count errors, and perhaps a histogram for the duration of failed invocations as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[JBoss JIRA] (ISPN-12102) Validate configuration before storing it
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12102?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12102:
-----------------------------------
Fix Version/s: 12.0.0.Dev05
(was: 12.0.0.Dev04)
> Validate configuration before storing it
> ----------------------------------------
>
> Key: ISPN-12102
> URL: https://issues.redhat.com/browse/ISPN-12102
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 11.0.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 12.0.0.Dev05
>
>
> Although {{ConfigurationBuilder}} does some validation, sometimes it needs something more. As an example, the cross-site replication needs a running {{Transport}} to check if xsite is really supported.
> As a side effect, the console is broken when you try to define the following cache without {{RELAY2}} being present in the JGroups stack.
> {code:xml}
> <infinispan>
> <cache-container>
> <distributed-cache name="xsite">
> <backups>
> <backup site="site2"/>
> </backups>
> </distributed-cache>
> </cache-container>
> </infinispan>
> {code}
> This happens because the {{Configuration}} is stored and the {{Cache}} with the exception is stored as well.
> The fix proposed it adds a method to {{ModuleLifecyle}} where the {{Configuration}} can be validated before it is store in the "global state".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months