|
| 1 | +# Oracle Feature Store (ADS) |
| 2 | + |
| 3 | +[](https://pypi.org/project/oracle-ads/) [](https://docs.oracle.com/en-us/iaas/data-science/using/conda-pyspark-fam.htm) [](https://github.com/oracle-samples/oci-data-science-ai-samples/tree/master/notebook_examples) [](https://delta.io/) [](https://spark.apache.org/docs/3.2.1/api/python/index.html) [](https://greatexpectations.io/) [](https://pandas.pydata.org/) [](https://arrow.apache.org/docs/python/index.html) |
| 4 | + |
| 5 | +Managing many datasets, data sources, and transformations for machine learning is complex and costly. Poorly cleaned data, data issues, bugs in transformations, data drift, and training serving skew all lead to increased model development time and poor model performance. Feature store solves many of the problems because it is a centralized way to transform and access data for training and serving time, Feature stores help define a standardised pipeline for ingestion of data and querying of data. |
| 6 | + |
| 7 | +ADS feature store is a stack-based solution that is deployed in your tenancy using OCI Resource Manager. |
| 8 | + |
| 9 | +Following are brief descriptions of key concepts and the main components of ADS feature store. |
| 10 | + |
| 11 | +- ``Feature Vector``: Set of feature values for any one primary and identifier key. For example, all and a subset of features of customer ID 2536 can be called as one feature vector . |
| 12 | +- ``Feature``: A feature is an individual measurable property or characteristic of an event being observed. |
| 13 | +- ``Entity``: An entity is a group of semantically related features. The first step a consumer of features would typically do when accessing the feature store service is to list the entities and the entities associated with features. Another way to look at it is that an entity is an object or concept that's described by its features. Examples of entities are customer, product, transaction, review, image, document, and so on. |
| 14 | +- ``Feature Group``: A feature group in a feature store is a collection of related features that are often used together in ML models. It serves as an organizational unit within the feature store for users to manage, version, and share features across different ML projects. By organizing features into groups, data scientists and ML engineers can efficiently discover, reuse, and collaborate on features reducing the redundant work and ensuring consistency in feature engineering. |
| 15 | +- ``Feature Group Job``: Feature group jobs are the processing instance of a feature group. Each feature group job includes validation results and statistics results. |
| 16 | +- ``Dataset``: A dataset is a collection of features that are used together to either train a model or perform model inference. |
| 17 | +- ``Dataset Job``: A dataset job is the processing instance of a dataset. Each dataset job includes validation results and statistics results. |
| 18 | + |
| 19 | +## Documentation |
| 20 | + |
| 21 | + - [Oracle Feature Store SDK (ADS) Documentation](https://feature-store-accelerated-data-science.readthedocs.io/en/latest/) |
| 22 | + - [OCI Data Science and AI services Examples](https://github.com/oracle/oci-data-science-ai-samples) |
| 23 | + - [Oracle AI & Data Science Blog](https://blogs.oracle.com/ai-and-datascience/) |
| 24 | + - [OCI Documentation](https://docs.oracle.com/en-us/iaas/data-science/using/data-science.htm) |
| 25 | + |
| 26 | +## Examples |
| 27 | + |
| 28 | +### Quick start examples |
| 29 | + |
| 30 | +| Jupyter Notebook | Description | |
| 31 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |
| 32 | +| [Feature store querying](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_querying.ipynb) | - Ingestion, querying and exploration of data. | |
| 33 | +| [Feature store quickstart](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_quickstart.ipynb) | - Ingestion, querying and exploration of data. | |
| 34 | +| [Schema enforcement and schema evolution](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_schema_evolution.ipynb) | - `Schema evolution` allows you to easily change a table's current schema to accommodate data that is changing over time. `Schema enforcement`, also known as schema validation, is a safeguard in Delta Lake that ensures data quality by rejecting writes to a table that don't match the table's schema. | |
| 35 | +| [Storage of medical records in feature store](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_ehr_data.ipynb) | Example to demonstrate storage of medical records in feature store | |
| 36 | + |
| 37 | +### Big data operations using OCI DataFlow |
| 38 | + |
| 39 | +| Jupyter Notebook | Description | |
| 40 | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| |
| 41 | +| [Big data operations with feature store](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_spark_magic.ipynb) | - Ingestion of data using Spark Magic, querying and exploration of data using Spark Magic. | |
| 42 | + |
| 43 | +### LLM Use cases |
| 44 | + |
| 45 | +| Jupyter Notebook | Description | |
| 46 | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| |
| 47 | +| [Embeddings in Feature Store](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_embeddings.ipynb) | - `Embedding feature stores` are optimized for fast and efficient retrieval of embeddings. This is important because embeddings can be high-dimensional and computationally expensive to calculate. By storing them in a dedicated store, you can avoid the need to recalculate embeddings for the same data repeatedly. | |
| 48 | +| [Synthetic data generation in feature store using OpenAI and FewShotPromptTemplate](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_medical_synthetic_data_openai.ipynb) | - `Synthetic data` is artificially generated data, rather than data collected from real-world events. It's used to simulate real data without compromising privacy or encountering real-world limitations. | |
| 49 | +| [PII Data redaction, Summarise Content and Translate content using doctran and open AI](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_pii_redaction_and_transformation.ipynb) | - One way to think of Doctran is a LLM-powered black box where messy strings go in and nice, clean, labelled strings come out. Another way to think about it is a modular, declarative wrapper over OpenAI's functional calling feature that significantly improves the developer experience. | |
| 50 | +| [OpenAI embeddings in feature store](https://github.com/oracle-samples/oci-data-science-ai-samples/blob/main/notebook_examples/feature_store_embeddings_openai.ipynb) | - `Embedding feature stores` are optimized for fast and efficient retrieval of embeddings. This is important because embeddings can be high-dimensional and computationally expensive to calculate. By storing them in a dedicated store, you can avoid the need to recalculate embeddings for the same data repeatedly. | |
| 51 | + |
| 52 | + |
| 53 | +## Contributing |
| 54 | + |
| 55 | +This project welcomes contributions from the community. Before submitting a pull request, please [review our contribution guide](./../../CONTRIBUTING.md) |
| 56 | + |
| 57 | +Find Getting Started instructions for developers in [README-development.md](https://github.com/oracle/accelerated-data-science/blob/main/README-development.md) |
| 58 | + |
| 59 | +## Security |
| 60 | + |
| 61 | +Consult the security guide [SECURITY.md](https://github.com/oracle/accelerated-data-science/blob/main/SECURITY.md) for our responsible security vulnerability disclosure process. |
| 62 | + |
| 63 | +## License |
| 64 | + |
| 65 | +Copyright (c) 2020, 2022 Oracle and/or its affiliates. Licensed under the [Universal Permissive License v1.0](https://oss.oracle.com/licenses/upl/) |
0 commit comments