<div dir="auto">We can cut 9.1.6.Final today.<br><br><div data-smartmail="gmail_signature">--<br>Tristan Tarrant<br>Infinispan Lead & Data Grid Architect<br>Red Hat</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 13 Feb 2018 14:21, "Paul Ferraro" <<a href="mailto:paul.ferraro@redhat.com">paul.ferraro@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Can one of the devs please review this patch?<br>
<a href="https://github.com/infinispan/infinispan/pull/5750" rel="noreferrer" target="_blank">https://github.com/infinispan/<wbr>infinispan/pull/5750</a><br>
<br>
The limit of cache names sizes to 127 bytes is too limiting for<br>
hibernate/JPA 2nd level cache deployments, which generate cache names<br>
using fully qualified class names of entity classes, which are user<br>
generated thus can easily exceed 128 bytes (but are far less likely to<br>
exceed 255). This is exacerbated by the JPA integration, which<br>
additionally appends the deployment name. We have a long term<br>
solution for this, but in the meantime, the above patch is sufficient<br>
to pass the TCK.<br>
<br>
We'll also need a 9.1.6.Final release ASAP, lest we revert back to<br>
Infinispan 8.2.x for WF12, the feature freeze for which is tomorrow<br>
(they are considering this upgrade a feature, given the scope of its<br>
impact).<br>
<br>
Thanks,<br>
<br>
Paul<br>
______________________________<wbr>_________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br>
</blockquote></div></div>