You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pegasus.apache.org by GitBox <gi...@apache.org> on 2021/05/31 09:18:38 UTC

[GitHub] [incubator-pegasus] levy5307 edited a comment on pull request #739: feat: implement value_schema_manager::get_value_schema

levy5307 edited a comment on pull request #739:
URL: https://github.com/apache/incubator-pegasus/pull/739#issuecomment-851350250


   > The old `value_schema` is a table level concept defined in `data_version` in meta column family. Now, `value_schema` version 2 updates it, `value_schema` becomes a value level concept, a table is permitted having different value schema. However, it will raise two problems.
   > The first problem is the compatibility problem. New server version won't be downgraded because the old server can not figure out value_schema version 2 data. I think it is okay for new server can not downgrade, but our recent releases are almost all not-downgraded, should we merge this commit into master branch?
   > The second problem is the `data_version` in meta cf. This value is actually useless for new server, but it can not be removed for version0 and version1, would you have any solution to remove this value in future?
   
   I don't think so. Because value_schema version 2 will not updates data version in meta column family. It only reads from it.


-- 
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: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org