You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Noble Paul (Jira)" <ji...@apache.org> on 2019/12/17 23:37:00 UTC
[jira] [Comment Edited] (SOLR-14095) Remove serialization and/or
support serialization filtering
[ https://issues.apache.org/jira/browse/SOLR-14095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998674#comment-16998674 ]
Noble Paul edited comment on SOLR-14095 at 12/17/19 11:36 PM:
--------------------------------------------------------------
I was trying to eliminate that one. But is the change backward compatible? But , we should always stick to JSON wherever possible.
We do not use javabin in any of the ZK content. Let's only use human readable format there. Our ops guys read it manually or use non-java tools to manage their Solr clusters. They can't parse a javabin payload
was (Author: noble.paul):
I was trying to eliminate that one. But is the change backward compatible? But , we should always stick to JSON whereever possible
> Remove serialization and/or support serialization filtering
> -----------------------------------------------------------
>
> Key: SOLR-14095
> URL: https://issues.apache.org/jira/browse/SOLR-14095
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Robert Muir
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Removing the use of serialization is greatly preferred.
> But if serialization over the wire must really happen, then we must use JDK's serialization filtering capability to prevent havoc.
> https://docs.oracle.com/javase/10/core/serialization-filtering1.htm#JSCOR-GUID-3ECB288D-E5BD-4412-892F-E9BB11D4C98A
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org