简体   繁体   English

vdm Odata版本兼容性

[英]vdm Odata version compatibility

A conceptual question for vdm usage. vdm使用的概念性问题。 Assume my OData evolves in a S4 cloud system and I am consuming it in a microservice. 假设我的OData在S4云系统中演进,而我在微服务中使用它。 Since vdm needs the edmx file to generate entitiy classes, assume my odata has a new field or has eliminated one field that I do not use. 由于vdm需要edmx文件生成实体类,因此假设我的odata有一个新字段或已删除了一个我不使用的字段。 If I do not change my edmx and will not generate new classes, will it be still work my call? 如果我不更改edmx并且不会生成新的类,那么它仍然可以正常使用吗? And second question is, if one of the fields I use change, and I need to ensure 0 downtime, how do I handle 2 versions of generated classes in the same time? 第二个问题是,如果我使用的字段之一发生更改,并且我需要确保停机时间为0,那么如何同时处理生成的类的2个版本?

The generated OData VDM ultimately performs an OData call based on the fields that are used. 生成的OData VDM最终根据使用的字段执行OData调用。 So if you would not use fields that are removed, this should not be a problem. 因此,如果您不使用已删除的字段,则应该不会有问题。 Note however, that such removals would have to be done in a new version of the SAP S/4HANA service. 但是请注意,必须在新版本的SAP S / 4HANA服务中进行此类删除。

Since breaking changes affect all consumers independent of whether the Java or JavaScript VDM of the SAP S/4HANA Cloud SDK is used, developers of services in SAP S/4HANA have to follow a certain API guideline that includes specific deprecation rules. 由于重大更改会影响所有使用者,而与是否使用SAP S / 4HANA Cloud SDK的Java或JavaScript VDM无关,因此SAP S / 4HANA中的服务开发人员必须遵循特定的API指南,其中包括特定的弃用规则。

So, if a breaking change is really required, according to the S/4HANA API guideline, a new version of the service has to be published and this will be also available with a different URL. 因此,如果确实需要进行重大更改,则根据S / 4HANA API指南,必须发布该服务的新版本,并且该版本也可以通过其他URL获得。 This then gives you the possibility to migrate from an old to a new version without interruptions. 这样,您就可以不受干扰地从旧版本迁移到新版本。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM