[ https://issues.redhat.com/browse/IPROTO-161?page=com.atlassian.jira.plugi... ]
Nistor Adrian commented on IPROTO-161:
--------------------------------------
I've fixed this in protostream and will release today 4.3.4.Final
> Maven compiler plugin 3.8.1 and Protostream seem broken
> -------------------------------------------------------
>
> Key: IPROTO-161
> URL: https://issues.redhat.com/browse/IPROTO-161
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Affects Versions: 4.3.3.Final
> Reporter: Katia Aresti
> Assignee: Nistor Adrian
> Priority: Blocker
> Fix For: 4.4.0.Alpha1, 4.3.4.Final
>
>
> Coming from a Quarkus issue, the maven compiler plugin in version 3.8.1 seems not working properly with classes compilation and generation
>
> Check the Quarkus issue.
>
> [https://github.com/quarkusio/quarkus/issues/9980]
>
> This might be a library problem or a maven problem
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[ https://issues.redhat.com/browse/IPROTO-161?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated IPROTO-161:
---------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/protostream/pull/106
> Maven compiler plugin 3.8.1 and Protostream seem broken
> -------------------------------------------------------
>
> Key: IPROTO-161
> URL: https://issues.redhat.com/browse/IPROTO-161
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Affects Versions: 4.3.3.Final
> Reporter: Katia Aresti
> Assignee: Nistor Adrian
> Priority: Blocker
> Fix For: 4.4.0.Alpha1, 4.3.4.Final
>
>
> Coming from a Quarkus issue, the maven compiler plugin in version 3.8.1 seems not working properly with classes compilation and generation
>
> Check the Quarkus issue.
>
> [https://github.com/quarkusio/quarkus/issues/9980]
>
> This might be a library problem or a maven problem
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[ https://issues.redhat.com/browse/IPROTO-161?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated IPROTO-161:
---------------------------------
Fix Version/s: 4.4.0.Alpha1
> Maven compiler plugin 3.8.1 and Protostream seem broken
> -------------------------------------------------------
>
> Key: IPROTO-161
> URL: https://issues.redhat.com/browse/IPROTO-161
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Affects Versions: 4.3.3.Final
> Reporter: Katia Aresti
> Assignee: Nistor Adrian
> Priority: Blocker
> Fix For: 4.4.0.Alpha1, 4.3.4.Final
>
>
> Coming from a Quarkus issue, the maven compiler plugin in version 3.8.1 seems not working properly with classes compilation and generation
>
> Check the Quarkus issue.
>
> [https://github.com/quarkusio/quarkus/issues/9980]
>
> This might be a library problem or a maven problem
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[ https://issues.redhat.com/browse/ISPN-10216?page=com.atlassian.jira.plugi... ]
Will Burns reassigned ISPN-10216:
---------------------------------
Assignee: Will Burns
> Implement bloom filter based near cache invalidations
> -----------------------------------------------------
>
> Key: ISPN-10216
> URL: https://issues.redhat.com/browse/ISPN-10216
> Project: Infinispan
> Issue Type: Sub-task
> Components: Hot Rod, Listeners
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
>
> Currently our near cache invalidation messages contain every remove/modify/expired event. It would be preferable to only send known invalidation messages to the client using some sort of bloom filter based approach. This should help reduce the number of total messages and allow for write clients to operate more efficiently.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
[ https://issues.redhat.com/browse/ISPN-10216?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-10216:
------------------------------
Status: Open (was: New)
> Implement bloom filter based near cache invalidations
> -----------------------------------------------------
>
> Key: ISPN-10216
> URL: https://issues.redhat.com/browse/ISPN-10216
> Project: Infinispan
> Issue Type: Sub-task
> Components: Hot Rod, Listeners
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
>
> Currently our near cache invalidation messages contain every remove/modify/expired event. It would be preferable to only send known invalidation messages to the client using some sort of bloom filter based approach. This should help reduce the number of total messages and allow for write clients to operate more efficiently.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)