Správa normalizačního kódu
- Správa kódu
- Jak si prohlédnout aktuální kód - prohlížeč v AUI a kde to najdu na disku
- Úprava existujícího kódu
- zmínit i následky jako potřebu recompute atp.
- Přidání nového modulu
Obsah se týká něčeho trochu jiného, není použitelný. Popsat výše zmíněné v Admin UI a deploymentu.
Changing a pipeline is as simple as changing the configuration file and applying the configuration.
If doing some quick and temporary changes you can also use a shortcut. Normalizer configuration can
be reloaded via API call in the developer console. A typical use-case is when you need to disable a
pipeline, perform some maintenance and then re-enable the pipeline. In such scenario, you modify the
configuration in-place within the currently active deployment on the host and then execute
Normalizer.reload_config() in the developer console. This will reload and apply Normalizer
configuration while the rest of ALTWORX is unaffected.
When changing the Pipeline definition beware that the change is applied from the moment ALTWORX reloads the configuration. Therefore, you might end up with a topic that contains both old and new format of the data. This might not be what you are looking for.
If the change is not backwards compatible or if you want to apply to all data incl. history, you can create a new version of the topic. This will enable you to keep the new data next to the old. You can have both normalizers (the new and the original) running thus minimizing the downtime and easing the migration to the new Runtime topic. For details about topic versions see Configuration section.
Another option is to re-normalize/recompute the whole topic. This is useful if you don’t mind the downtime or if you prefer not to increase the topic version. See Lifecycle sections for details about recomputation.