lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Updated] (LUCENE-6713) TooComplexToDeterminizeException claims to be serializable but actually isn't?
Date Tue, 04 Aug 2015 14:32:04 GMT


Michael McCandless updated LUCENE-6713:
    Attachment: LUCENE-6713.patch


At first I didn't like adding transient to the members here, since it would "secretly" create
null fields on the receiving end, but then I noticed we init the exception message with the
offending RegExp, so net/net I think this is a good solution.

> TooComplexToDeterminizeException claims to be serializable but actually isn't?
> ------------------------------------------------------------------------------
>                 Key: LUCENE-6713
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>         Attachments: LUCENE-6713.patch
> This custom exception class, added in LUCENE-6046, claims to be {{Serializable}} since
in inherits from {{Throwable}} yet if you try to serialize it you'll hit runtime exceptions
because its members don't implement {{Serializable}}.
> We intentionally pushed Java serialization requirements out of Lucene a while back (LUCENE-2908),
but maybe for custom exception classes which unfortunately necessarily claim to implement
{{Serializable}} we need to do something?
> We could just mark the members transient here, but that would mean when you unserialize
you get null members on the other end, e.g. you would no longer know which {{RegExp}} was
problematic ...

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message