You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by GitBox <gi...@apache.org> on 2021/04/15 02:48:57 UTC

[GitHub] [incubator-doris] caiconghui commented on pull request #5644: [Optimize]not need to deserialize twice

caiconghui commented on pull request #5644:
URL: https://github.com/apache/incubator-doris/pull/5644#issuecomment-820017839


   > > `Deserialization` here may be necessary. To ensure the tablet meta that will be stored in rocksdb is no problem and can be deserialized successfully, so deserializing the `meta_binary` here before saving it into rocksdb.
   > > I think it may be not a good practice to remove this part of the code.
   > 
   > I'm confused if it is possible that `SerializeToString` successfully but `ParseFromString` failed, maybe there are some historical reason?
   
   I think it make no sense to check that SerializeToString successfully but ParseFromString failed, because the next step is fatal error.  the result is the same as we store it to rocksdb and get it  then ParseFromString, finally fatal error.  what's more, until now, I could not see any fatal error like 'SerializeToString successfully but ParseFromString failed', may it is a bug in older version?
   
   I think  SerializeToString performance is very important ,which may affect many operations on tablet, like publish version etc.
   So,just need to do the simple thing to SerializeToString instead of  adding ParseFromString check which would may cause poor performance


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org