Skip to content

Commit 103637a

Browse files
committed
doc update-expectation,policy minor change
1 parent f84f16d commit 103637a

File tree

2 files changed

+44
-24
lines changed

2 files changed

+44
-24
lines changed

ads/feature_store/docs/source/feature_group.rst

Lines changed: 29 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -152,24 +152,45 @@ Feature store provides an API similar to Pandas to join feature groups together
152152
153153
Save expectation entity
154154
=======================
155-
With a ``FeatureGroup`` instance, we can save the expectation entity using ``save_expectation()``
155+
With a ``FeatureGroup`` instance, You can save the expectation details using ``with_expectation_suite()`` with parameters
156+
157+
- ``expectation_suite: ExpectationSuite``. ExpectationSuit of great expectation
158+
- ``expectation_type: ExpectationType``. Type of expectation
159+
- ``ExpectationType.STRICT``: Fail the job if expectation not met
160+
- ``ExpectationType.LENIENT``: Pass the job even if expectation not met
156161

157162
.. note::
158163

159164
Great Expectations is a Python-based open-source library for validating, documenting, and profiling your data. It helps you to maintain data quality and improve communication about data between teams. Software developers have long known that automated testing is essential for managing complex codebases.
160165

161166
.. image:: figures/validation.png
162167

163-
The ``.save_expectation()`` method takes the following optional parameter:
168+
.. code-block:: python3
164169
165-
- ``expectation: Expectation``. Expectation of great expectation
166-
- ``expectation_type: ExpectationType``. Type of expectation
167-
- ``ExpectationType.STRICT``: Fail the job if expectation not met
168-
- ``ExpectationType.LENIENT``: Pass the job even if expectation not met
170+
expectation_suite = ExpectationSuite(
171+
expectation_suite_name="expectation_suite_name"
172+
)
173+
expectation_suite.add_expectation(
174+
ExpectationConfiguration(
175+
expectation_type="expect_column_values_to_not_be_null",
176+
kwargs={"column": "<column>"},
177+
)
169178
170-
.. code-block:: python3
179+
feature_group_resource = (
180+
FeatureGroup()
181+
.with_feature_store_id(feature_store.id)
182+
.with_primary_keys(["<key>"])
183+
.with_name("<name>")
184+
.with_entity_id(entity.id)
185+
.with_compartment_id(<compartment_id>)
186+
.with_schema_details_from_dataframe(<datframe>)
187+
.with_expectation_suite(
188+
expectation_suite=expectation_suite,
189+
expectation_type=ExpectationType.STRICT,
190+
)
191+
)
171192
172-
feature_group.save_expectation(expectation_suite, expectation_type="STRICT")
193+
You can call the ``get_validation_output()`` method of the FeatureGroup instance to fetch validation results for a specific ingestion job.
173194

174195
Statistics Results
175196
==================
@@ -192,7 +213,6 @@ With a FeatureGroup instance, we can get the last feature group job details usin
192213
193214
# Fetch validation results for a feature group
194215
feature_group_job = feature_group.get_last_job()
195-
feature_group_job.get_validation_output_df()
196216
197217
Get features
198218
=============

ads/feature_store/docs/source/terraform.rst

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -30,21 +30,21 @@ Feature Store users need to provide the following access permissions in order to
3030
3131
define tenancy <feature store service tenancy> as <feature store service tenancy ocid>
3232
endorse group <feature store user group> to read repos in tenancy <feature store service tenancy>
33-
allow group <feature store user group> to manage orm-stacks in compartment <compartmentId>
34-
allow group <feature store user group> to manage orm-jobs in compartment <compartmentId>
35-
allow group <feature store user group> to manage object-family in compartment <compartmentId>
36-
allow group <feature store user group> to manage users in compartment <compartmentId>
37-
allow group <feature store user group> to manage instance-family in compartment <compartmentId>
38-
allow group <feature store user group> to manage tag-namespaces in compartment <compartmentId>
39-
allow group <feature store user group> to manage groups in compartment <compartmentId>
40-
allow group <feature store user group> to manage policies in compartment <compartmentId>
41-
allow group <feature store user group> to manage dynamic-groups in compartment <compartmentId>
42-
allow group <feature store user group> to manage virtual-network-family in compartment <compartmentId>
43-
allow group <feature store user group> to manage functions-family in compartment <compartmentId>
44-
allow group <feature store user group> to inspect compartments in compartment <compartmentId>
45-
allow group <feature store user group> to manage cluster-family in compartment <compartmentId>
46-
allow group <feature store user group> to manage mysql-family in compartment <compartmentId>
47-
allow group <feature store user group> to manage api-gateway-family in compartment <compartmentId>
33+
allow group <feature store user group> to manage orm-stacks in compartment <compartmentName>
34+
allow group <feature store user group> to manage orm-jobs in compartment <compartmentName>
35+
allow group <feature store user group> to manage object-family in compartment <compartmentName>
36+
allow group <feature store user group> to manage users in compartment <compartmentName>
37+
allow group <feature store user group> to manage instance-family in compartment <compartmentName>
38+
allow group <feature store user group> to manage tag-namespaces in compartment <compartmentName>
39+
allow group <feature store user group> to manage groups in compartment <compartmentName>
40+
allow group <feature store user group> to manage policies in compartment <compartmentName>
41+
allow group <feature store user group> to manage dynamic-groups in compartment <compartmentName>
42+
allow group <feature store user group> to manage virtual-network-family in compartment <compartmentName>
43+
allow group <feature store user group> to manage functions-family in compartment <compartmentName>
44+
allow group <feature store user group> to inspect compartments in compartment <compartmentName>
45+
allow group <feature store user group> to manage cluster-family in compartment <compartmentName>
46+
allow group <feature store user group> to manage mysql-family in compartment <compartmentName>
47+
allow group <feature store user group> to manage api-gateway-family in compartment <compartmentName>
4848
4949
Deploy Using Oracle Resource Manager
5050
====================================

0 commit comments

Comments
 (0)