Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add partial data loading #1248

Merged
merged 13 commits into from
Jan 24, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
126 changes: 126 additions & 0 deletions guides/integrations-api/general-concepts/partial-data-loading.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,126 @@
---
nav:
title: Partial Data Loading
position: 50

---

# Partial Data Loading

`Partial data loading` allows you to select specific fields of an entity to be returned by the API. This can be useful if you only need a few fields of an entity and don't want to load the whole entity. This can reduce the response size and improve the performance of your application.

### Partial data loading vs Includes

`Partial data loading` is different from the [includes](./search-criteria.md#includes-apialias) feature. The `includes` works as post-output processing, so the complete entity or data is loaded in the backend side and then filtered, while `partial data loading` works already on database level. This means that the database only loads the requested fields and not the whole entity.

## Usage

```http
POST /api/search/currency
Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json
Accept: application/json

{
"fields": [
"name"
]
}
```

```json
// response
{
"total": 1,
"data": [
{
"extensions": [],
"_uniqueIdentifier": "018cda3ac909712496bccc065acf0ff4",
"translated": {
"name": "US-Dollar"
},
"id": "018cda3ac909712496bccc065acf0ff4",
"name": "US-Dollar",
"isSystemDefault": false,
"apiAlias": "currency"
}
],
"aggregations": []
}
```

Fields can also reference fields of associations like in this example the assigned salesChannel names of the currency. The API adds the necessary associations automatically.

```http
POST /api/search/currency
Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json
Accept: application/json

{
"fields": [
"name",
"salesChannels.name"
]
}
```

```json
// response
{
"total": 1,
"data": [
{
"extensions": [],
"_uniqueIdentifier": "018cda3ac909712496bccc065acf0ff4",
"translated": {
"name": "US-Dollar"
},
"id": "018cda3ac909712496bccc065acf0ff4",
"name": "US-Dollar",
"salesChannels": [
{
"extensions": [],
"_uniqueIdentifier": "018cda3af56670d6a3fa515a85967bd2",
"translated": {
"name": "Storefront"
},
"id": "018cda3af56670d6a3fa515a85967bd2",
"name": "Storefront",
"apiAlias": "sales_channel"
}
],
"isSystemDefault": false,
"apiAlias": "currency"
}
],
"aggregations": []
}
```

## Default fields

Some fields are always loaded like the `id` or join relevant fields like foreign keys, these are necessary for the API to work correctly and can't be removed.

## Runtime fields

Some fields in the API are generated at runtime like `isSystemDefault` of the currency. These fields are loaded by default when the referenced data is available, otherwise they can be requested in the `fields` parameter to force the API to load them.

For custom entity definitions with runtime flag, the referenced fields need to be specified inside the constructor. See an example from the core:

```php

Check warning on line 111 in guides/integrations-api/general-concepts/partial-data-loading.md

View workflow job for this annotation

GitHub Actions / LanguageTool

[LanguageTool] guides/integrations-api/general-concepts/partial-data-loading.md#L111

File types are normally capitalized. (FILE_EXTENSIONS_CASE[1]) Suggestions: `PHP` URL: https://languagetool.org/insights/post/spelling-capital-letters/ Rule: https://community.languagetool.org/rule/show/FILE_EXTENSIONS_CASE?lang=en-US&subId=1 Category: CASING
Raw output
guides/integrations-api/general-concepts/partial-data-loading.md:111:3: File types are normally capitalized. (FILE_EXTENSIONS_CASE[1])
 Suggestions: `PHP`
 URL: https://languagetool.org/insights/post/spelling-capital-letters/ 
 Rule: https://community.languagetool.org/rule/show/FILE_EXTENSIONS_CASE?lang=en-US&subId=1
 Category: CASING
protected function defineFields(): FieldCollection
{
return new FieldCollection([
(new IdField('id', 'id'))->addFlags(new ApiAware(), new PrimaryKey(), new Required()),
(new StringField('path', 'path'))->addFlags(new ApiAware()),

// When this field is requested, we need the data of path field to generate the url
(new StringField('url', 'url'))->addFlags(new ApiAware(), new Runtime(['path'])),
]);
}
```

## Limitations

The current limitation of the `partial data loading` is that it only works on the Entity level. Any custom responses like a product detail page or CMS in the Store API can't be used with this feature, as the Store API needs the whole entity to generate the response. If you need a small response, we recommend using the [includes](./search-criteria.md#includes-apialias) feature of the Search API.
Loading