--- title: January 2024 versions: cdsjs: 7.6.1 cdsdk: 7.6.0 cdsc: 4.6.2 cdsmtxs: 1.15.0 java: 2.6.1 --- # January 2024 [[toc]] ## Open Telemetry Plugin The Telemetry plugin [@cap-js/telemetry](https://www.npmjs.com/package/@cap-js/telemetry) provides observability features such as tracing and metrics, including [automatic OpenTelemetry instrumentation](https://opentelemetry.io/docs/concepts/instrumentation/automatic). Simply add the plugin to your project and you will find telemetry output written to the console as follows: ```txt [odata] - GET /odata/v4/processor/Incidents [telemetry] - elapsed times: 0.00 → 2.85 = 2.85 ms GET /odata/v4/processor/Incidents 0.47 → 1.24 = 0.76 ms ProcessorService - READ ProcessorService.Incidents 0.78 → 1.17 = 0.38 ms db - READ ProcessorService.Incidents 0.97 → 1.06 = 0.09 ms @cap-js/sqlite - prepare SELECT json_object('ID',ID,'createdAt',createdAt,'creat… 1.10 → 1.13 = 0.03 ms @cap-js/sqlite - stmt.all SELECT json_object('ID',ID,'createdAt',createdAt,'crea… 1.27 → 1.88 = 0.61 ms ProcessorService - READ ProcessorService.Incidents.drafts 1.54 → 1.86 = 0.32 ms db - READ ProcessorService.Incidents.drafts 1.74 → 1.78 = 0.04 ms @cap-js/sqlite - prepare SELECT json_object('ID',ID,'DraftAdministrativeData_Dra… 1.81 → 1.85 = 0.04 ms @cap-js/sqlite - stmt.all SELECT json_object('ID',ID,'DraftAdministrativeData_Dr… ``` In addition to the default console output, there are predefined kinds for exporting telemetry data to [SAP Cloud Logging](https://help.sap.com/docs/cloud-logging), Dynatrace, and Jaeger. [See the repository's `README` for more details.](https://github.com/cap-js/telemetry/blob/main/README.md){ .learn-more} [Learn more about Java support.](/@external/java/operating-applications/observability#open-telemetry){ .learn-more} ## CDS Language & Compiler {#cds} ### Define Event by Projection You can now define an event as projection on an entity, type, or another event. This is useful, for example, when importing services: it allows to define an event in CAP as projection on the "external" event. Example: ```cds event CustomerChanged : projection on ImportedService.BusinessPartner.ChangedEvent { BusinessPartner as ID, BusinessPartnerFullName as name, // ... } ``` Only the effective signature of the projection is relevant. [Learn more about **Events**.](/@external/cds/cdl#events){ .learn-more} ## Node.js {#cds-js} ### Media Data and Large Binaries Previously, the database services returned `cds.LargeBinary` without `@Core.MediaType` annotation as regular column with base64-encoded buffer as value which potentially causes problems in memory consumption. As a consequence, from now on the database services will return large binaries only if requested explicitly and as a stream instead of the materialized buffer. This has the following effect: ```js SELECT.from(Attachments) //> [{ ID, title, image: Buffer }] [!code --] SELECT(['image']).from(Attachments) //> [{ image: Buffer }] [!code --] SELECT.from(Attachments) //> does not include "image" [!code ++] SELECT(['image']).from(Attachments) //> [{ image: }] [!code ++] ``` This also has an effect for OData APIs. Large binaries have to be annotated with `@Core.MediaType` in order to be reachable via the [streaming choreography](/@external/guides/services/media-data). If not annotated, those properties are not reachable anymore, even if requested explicitely. `cds.stream()` and `srv.stream()` are deprecated and will be removed with the next major release. `SELECT` with a single large binary column can be used instead as described above. Compatibility to the previous behavior can be restored with ```json "cds": { "features": { "stream_compat": true } } ``` :::tip It is strongly recommended to annotate all large binary properties with `@Core.MediaType` and use them according to streaming scenarios. ::: [Learn more about streaming.](/@external/guides/services/media-data){ .learn-more} [Learn more about databases.](/@external/guides/databases/index){ .learn-more} ### Programmatic Outboxing of Services You can now use `cds.outboxed(srv)` to get the outboxed variant of a service: Each event first gets stored in an outbox before reaching the target service. For immediate emits of outboxed services, there's also the counterpart `cds.unboxed(srv)`. ```js const outboxed = cds.outboxed(srv) await outboxed.emit('someEvent', { some: 'message' }) //> deferred emit via outbox await cds.unboxed(outboxed).emit('someEvent', { some: 'message' }) //> immediate emit w/o outbox ``` [Learn more about the outbox in Node.js.](/@external/node.js/event-queues){ .learn-more} ### Lean Draft Sorting on SAP Fiori List Report Floorplan The sorting behavior for the lean draft has been aligned with the other runtimes in the SAP ecosystem, such as CAP Java and RAP for a consistent user experience. Instead of positioning the drafts always on top of the list, they are now included at the respective position of the actual sorting order.