You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/fhir/fhir-best-practices.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,7 @@ To achieve optimal performance with the import operation, consider the following
28
28
***Do** use large files while ingesting data. The optimal NDJSON file size for import is 50 MB or larger (or 20,000 resources or more, with no upper limit). Combining smaller files into larger ones can enhance performance.
29
29
***Consider** using the import operation over HTTP API requests to ingest the data into FHIR service. The import operation provides a high throughput and is a scalable method for loading data.
30
30
***Consider** importing all FHIR resource files in a single import operation for optimal performance. Aim for a total file size of 100 GB or more (or 100 million resources, no upper limit) in one operation. Maximizing an import in this way helps reduce the overhead associated with managing multiple import jobs.
31
+
***Consider** performing import job with the resources mapping to the same resource type for better throughput.
31
32
***Consider** running multiple concurrent imports only if necessary, but limit parallel import jobs. A single large import is designed to consume all available system resources, and processing throughput doesn't increase with concurrent import jobs.
@@ -360,6 +360,12 @@ Then, for each file or class affected by the incident, you can jump into the sou
360
360
361
361
## Release notes
362
362
363
+
### 7.6.0.2
364
+
365
+
This release contains the following fixes.
366
+
367
+
-`java-removals-00150` rule is now triggering correctly.
368
+
363
369
### 7.6.0.1
364
370
365
371
This release contains the following fixes and enhancements.
@@ -425,6 +431,17 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
425
431
426
432
## Known Issues
427
433
434
+
### 7.6.0.2
435
+
436
+
- The flag `--overrideProviderSettings` isn't supported.
437
+
- Rules issues:
438
+
-`azure-system-config-01000`, `http-session-01000` rules aren't being triggered.
439
+
-`FileSystem - Java IO` rule isn't being triggered.
440
+
- Analyzing WAR files on Windows produces the following error: `Failed to Move Decompiled File`. An error occurs when analyzing WAR files on Windows, which is responsible for a few redundant incidents created on Windows OS.
441
+
- Error in Watcher Error channel on Windows: `Windows system assumed buffer larger than it is, events have likely been missed`. This error message appears on the command line during long-running jobs on Windows.
442
+
- <kbd>Ctrl</kbd>+<kbd>C</kbd> fails to stop ongoing analysis. To work around, manually terminate the process by explicitly killing the process.
443
+
- In binary analysis reports, the code snippet title shows an incorrect or non-existent file path.
444
+
428
445
### 7.6.0.1
429
446
430
447
- The flag `--overrideProviderSettings` isn't supported.
0 commit comments