Bug 1105103 - Infinispan query and remote query uses Externalizer ids in the same range as OGM leading to conflicts
Summary: Infinispan query and remote query uses Externalizer ids in the same range as ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER7
: 6.3.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1111391
TreeView+ depends on / blocked
 
Reported: 2014-06-05 11:48 UTC by Adrian Nistor
Modified: 2015-01-26 14:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1111391 (view as bug list)
Environment:
Last Closed: 2015-01-26 14:04:42 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-4345 0 Blocker Resolved Infinispan Query module needs to use a free Externalizer ID range 2014-06-20 07:31:50 UTC
Red Hat Issue Tracker ISPN-4350 0 Major Resolved Infinispan remote query server module needs to use a free Externalizer ID range 2014-06-20 07:31:50 UTC

Description Adrian Nistor 2014-06-05 11:48:16 UTC 
Need to backport ISPN-4350 and ISPN-4345
Comment 2 Adrian Nistor 2014-06-05 12:06:16 UTC 
PR here: https://github.com/infinispan/jdg/pull/116
Comment 3 Martin Gencur 2014-06-19 15:00:18 UTC 
This BZ probably needs a change in documentation in this chapter: http://docbuilder.usersys.redhat.com/12540/#sect-Custom_Externalizer_ID_Values

The new ranges for embedded query and remote query should be added (the ranges  described in https://github.com/anistor/infinispan/blob/1ceb73038aeb9a83172fa685b52e5b3e049f6fed/documentation/src/main/asciidoc/user_guide/chapter-61-Marshalling.adoc#preassigned-externalizer-id-ranges )
Comment 4 Martin Gencur 2014-06-19 15:01:57 UTC 
IOW, this needs to be added in docu:
Infinispan Query Module: 1600 - 1699
Infinispan Remote Query Module: 1700 - 1799
Note You need to log in before you can comment on or make changes to this bug.