[jira] [Commented] (LUCENE-6713) TooComplexToDeterminizeException claims to be serializable but actually isn't?

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14658255#comment-14658255 ] 

ASF subversion and git services commented on LUCENE-6713:
---------------------------------------------------------

Commit 1694218 from [~mikemccand] in branch 'dev/trunk'
[ https://svn.apache.org/r1694218 ]

LUCENE-6713: TooComplexToDeterminizeException claims to be serializable but wasn't

> TooComplexToDeterminizeException claims to be serializable but actually isn't?
> ------------------------------------------------------------------------------
>
>                 Key: LUCENE-6713
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6713
>             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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org