dataforge-core 1.3.2__tar.gz → 1.3.4__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (33) hide show
  1. {dataforge_core-1.3.2/cli/dataforge_core.egg-info → dataforge_core-1.3.4}/PKG-INFO +2 -2
  2. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/README.md +1 -1
  3. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/pg_deploy.sql +25 -7
  4. {dataforge_core-1.3.2 → dataforge_core-1.3.4/cli/dataforge_core.egg-info}/PKG-INFO +2 -2
  5. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/pyproject.toml +1 -1
  6. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/LICENSE +0 -0
  7. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/MANIFEST.in +0 -0
  8. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/__init__.py +0 -0
  9. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/databricks_sql.py +0 -0
  10. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/importProject.py +0 -0
  11. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/main.py +0 -0
  12. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/mainConfig.py +0 -0
  13. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/miniSparky.py +0 -0
  14. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/pg.py +0 -0
  15. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/log4j2.properties +0 -0
  16. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/meta.yaml +0 -0
  17. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/outputs/feature_customer.yaml +0 -0
  18. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/relations.yaml +0 -0
  19. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/sources/tpch_customer.yaml +0 -0
  20. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/sources/tpch_lineitem.yaml +0 -0
  21. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/sources/tpch_nations.yaml +0 -0
  22. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/sources/tpch_orders.yaml +0 -0
  23. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/sources/tpch_part.yaml +0 -0
  24. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/sources/tpch_partsupp.yaml +0 -0
  25. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/sources/tpch_region.yaml +0 -0
  26. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/resources/project/sources/tpch_supplier.yaml +0 -0
  27. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge/util.py +0 -0
  28. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge_core.egg-info/SOURCES.txt +0 -0
  29. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge_core.egg-info/dependency_links.txt +0 -0
  30. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge_core.egg-info/entry_points.txt +0 -0
  31. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge_core.egg-info/requires.txt +0 -0
  32. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/cli/dataforge_core.egg-info/top_level.txt +0 -0
  33. {dataforge_core-1.3.2 → dataforge_core-1.3.4}/setup.cfg +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: dataforge-core
3
- Version: 1.3.2
3
+ Version: 1.3.4
4
4
  Summary: Command line compiler for dataforge core projects
5
5
  Author-email: Vadim Orlov <vorlov@dataforgelabs.com>
6
6
  Project-URL: Homepage, https://github.com/dataforgelabs/dataforge-core
@@ -23,7 +23,7 @@ Dynamic: license-file
23
23
  [DataForge](https://www.dataforgelabs.com) helps data analysts and engineers build and extend data solutions by leveraging modern software engineering principles.
24
24
 
25
25
  [![OSSRank](https://shields.io/endpoint?url=https://ossrank.com/shield/4025)](https://ossrank.com/p/4025)
26
- [![Publish & Test](https://img.shields.io/github/actions/workflow/status/dataforgelabs/dataforge-core/python-publish.yml?label=Publish%20%26%20Test&branch=main)](https://github.com/dataforgelabs/dataforge-core/actions/workflows/python-publish.yml)
26
+ [![Publish & Test](https://img.shields.io/github/actions/workflow/status/dataforgelabs/dataforge-core/python-publish.yml?label=Publish%20%26%20Test&event=release)](https://github.com/dataforgelabs/dataforge-core/actions/workflows/python-publish.yml)
27
27
 
28
28
 
29
29
  ## Understanding DataForge
@@ -4,7 +4,7 @@
4
4
  [DataForge](https://www.dataforgelabs.com) helps data analysts and engineers build and extend data solutions by leveraging modern software engineering principles.
5
5
 
6
6
  [![OSSRank](https://shields.io/endpoint?url=https://ossrank.com/shield/4025)](https://ossrank.com/p/4025)
7
- [![Publish & Test](https://img.shields.io/github/actions/workflow/status/dataforgelabs/dataforge-core/python-publish.yml?label=Publish%20%26%20Test&branch=main)](https://github.com/dataforgelabs/dataforge-core/actions/workflows/python-publish.yml)
7
+ [![Publish & Test](https://img.shields.io/github/actions/workflow/status/dataforgelabs/dataforge-core/python-publish.yml?label=Publish%20%26%20Test&event=release)](https://github.com/dataforgelabs/dataforge-core/actions/workflows/python-publish.yml)
8
8
 
9
9
 
10
10
  ## Understanding DataForge
@@ -1,4 +1,4 @@
1
- --Built: Fri May 2 15:34:43 UTC 2025
1
+ --Built: Thu Jun 26 21:22:36 UTC 2025
2
2
  CREATE SCHEMA IF NOT EXISTS meta;
3
3
  CREATE SCHEMA IF NOT EXISTS log;
4
4
  DO $$
@@ -3581,6 +3581,7 @@ DECLARE
3581
3581
  v_ret_relation_ids int[] := '{}';
3582
3582
  v_reverse_flag boolean;
3583
3583
  v_max_length int;
3584
+ v_alt_cardinality_paths_exist boolean = false;
3584
3585
  BEGIN
3585
3586
 
3586
3587
  in_start_path := COALESCE(in_start_path,'{}'::int[]);
@@ -3645,6 +3646,7 @@ IF v_max_level IS NULL THEN
3645
3646
  RETURN json_build_object('error',format('Remove aggregation or add OVER clause. Target source `%s`', meta.u_get_source_name(in_to_source_id) ));
3646
3647
  END IF;
3647
3648
  ELSE
3649
+ v_alt_cardinality_paths_exist = EXISTS(SELECT 1 FROM _paths WHERE cardinality != in_cardinality);
3648
3650
  DELETE FROM _paths WHERE cardinality != in_cardinality;
3649
3651
  END IF;
3650
3652
 
@@ -3681,7 +3683,8 @@ FOR v_level IN 1 .. v_max_level LOOP
3681
3683
  ELSE
3682
3684
  v_next_relation_id := null;
3683
3685
  END IF;
3684
- RETURN json_build_object('path',v_ret_path,'complete', true, 'relation_ids',v_ret_relation_ids, 'next', v_next_relation_id);
3686
+ RETURN json_build_object('path',v_ret_path,'complete', true, 'relation_ids',v_ret_relation_ids, 'next', v_next_relation_id,
3687
+ 'alt_cardinality_path_exist',v_alt_cardinality_paths_exist);
3685
3688
  END IF;
3686
3689
  END LOOP;
3687
3690
 
@@ -3920,16 +3923,31 @@ RETURN to_jsonb(in_datatype);
3920
3923
  END;
3921
3924
 
3922
3925
  $BODY$;
3923
- CREATE OR REPLACE FUNCTION meta.u_get_source_name(in_source_id int)
3926
+ CREATE OR REPLACE FUNCTION meta.u_get_source_name(in_source_id int, templatize_flag boolean = false)
3924
3927
  RETURNS text
3925
3928
  LANGUAGE plpgsql
3926
3929
  AS $function$
3927
3930
 
3931
+ DECLARE
3932
+ v_source_template_id int;
3933
+ v_source_name text;
3934
+
3928
3935
  BEGIN
3929
-
3930
- RETURN COALESCE(
3931
- (SELECT s.source_name FROM meta.source s WHERE s.source_id = in_source_id),
3932
- format('Unknown source_id=%s', in_source_id));
3936
+ SELECT s.source_name, s.source_template_id
3937
+ INTO v_source_name, v_source_template_id
3938
+ FROM meta.source s WHERE s.source_id = in_source_id;
3939
+
3940
+ IF v_source_name IS NULL THEN
3941
+ RETURN format('Unknown source_id=%s', in_source_id);
3942
+ END IF;
3943
+
3944
+ IF NOT templatize_flag OR v_source_template_id IS NULL THEN
3945
+ RETURN v_source_name;
3946
+ END IF;
3947
+
3948
+ RETURN COALESCE(
3949
+ (SELECT object_name FROM meta.object_template t WHERE t.object_template_id = v_source_template_id),
3950
+ format('Unknown source_template_id=%s', v_source_template_id));
3933
3951
 
3934
3952
  END;
3935
3953
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: dataforge-core
3
- Version: 1.3.2
3
+ Version: 1.3.4
4
4
  Summary: Command line compiler for dataforge core projects
5
5
  Author-email: Vadim Orlov <vorlov@dataforgelabs.com>
6
6
  Project-URL: Homepage, https://github.com/dataforgelabs/dataforge-core
@@ -23,7 +23,7 @@ Dynamic: license-file
23
23
  [DataForge](https://www.dataforgelabs.com) helps data analysts and engineers build and extend data solutions by leveraging modern software engineering principles.
24
24
 
25
25
  [![OSSRank](https://shields.io/endpoint?url=https://ossrank.com/shield/4025)](https://ossrank.com/p/4025)
26
- [![Publish & Test](https://img.shields.io/github/actions/workflow/status/dataforgelabs/dataforge-core/python-publish.yml?label=Publish%20%26%20Test&branch=main)](https://github.com/dataforgelabs/dataforge-core/actions/workflows/python-publish.yml)
26
+ [![Publish & Test](https://img.shields.io/github/actions/workflow/status/dataforgelabs/dataforge-core/python-publish.yml?label=Publish%20%26%20Test&event=release)](https://github.com/dataforgelabs/dataforge-core/actions/workflows/python-publish.yml)
27
27
 
28
28
 
29
29
  ## Understanding DataForge
@@ -3,7 +3,7 @@ requires = ["setuptools"]
3
3
  build-backend = "setuptools.build_meta"
4
4
  [project]
5
5
  name = "dataforge-core"
6
- version = "v1.3.2"
6
+ version = "v1.3.4"
7
7
  authors = [
8
8
  {name="Vadim Orlov", email="vorlov@dataforgelabs.com"}
9
9
  ]
File without changes
File without changes