Friday, 18 March 2022

HDI: returning multiple deployment errors

Problem:

Working with SAP HANA Cloud and HDI the tooling stopped at the first error and you had to fix them in the sequence the errors where thrown. All this one by one. This can lead to a lot of cycles that are time consuming and do not support the workflow one had in mind.

Solution:

With SAP HANA Cloud March 2022 the HDI can now return the first error it can detect per each “dependency branch”.

SAP HANA, SAP HANA Exam, SAP HANA Preparation, SAP HANA Learning, SAP HANA Career

In this schematic tree we would see 3 errors caused in various depths in the tree.

The HDI works through the individual branches until finished or with error message.

How can you activate this behaviour?

SAP HANA, SAP HANA Exam, SAP HANA Preparation, SAP HANA Learning, SAP HANA Career
Adding stop_on_error parameter

in the /db/package.json file you add to the start script the parameter as:

--parameter stop_on_error=false

The default behaviour of  HDI remains the same. So no coding that is expecting the previous behaviour is broken. The default of stop_on_error is TRUE.

SAP HANA, SAP HANA Exam, SAP HANA Preparation, SAP HANA Learning, SAP HANA Career
Two error caused by wrong syntax

As you can see in the sample the errors are reflected in Business Application Studio (BAS) with 2 highlighted HDBTABLE definitions.

Summary:

The new HDI parameter “stop on error” should allow the developer to reduce the cycle times with HDI and allow to find faster and easier typos or other errors within the design time objects.

Help will look like this, but the link is not public at this point in time:

SAP HANA, SAP HANA Exam, SAP HANA Preparation, SAP HANA Learning, SAP HANA Career
Preview on the help page

You may be interested in the other parameters as well.

No comments:

Post a Comment