> For the complete documentation index, see [llms.txt](https://lern.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lern.sunbird.org/use/developer-guide/ml-service/data-pipeline-flink-jobs/ml-user-delete/folder-structure.md).

# Folder Structure

Ml User Delete Service folder structure is designed to organize the different modules and files that constitute the ml user delete flink job. It follows a modular approach, facilitating easy management and development of the service.

### The structure is as follows

```
.  
│
└── ml-jobs
    ├── pom.xml
    └── ml-user-delete
        ├── pom.xml
        └── src
            ├── main
            │   ├── resources
            │   │   └── user-delete.conf
            │   └── scala
            │       └── org
            │           └── sunbird
            │               └── job
            │                   └── userdelete
            │                       ├── domain
            │                       │   └── Event.scala
            │                       ├── functions
            │                       │   └── UserDeleteFunction.scala
            │                       └── task
            │                           ├── UserDeleteConfig.scala
            │                           └── UserDeleteStreamTask.scala                           
            └── test
                ├── resources
                │   └── test.conf
                └── scala
                    └── org
                        └── sunbird
                            └── job
                                ├── fixture
                                │   ├── EventFixture.scala
                                │   └── LoadMongoData.scala
                                └── spec
                                    └── UserDeleteFunctionTestSpec.scala
       
```

**ml-jobs** 

This is the main directory that contains manage learn related Flink jobs.

**ml-user-delete**

This folder contains all the required directory for actual implementation of logics. 

**resources \[main]**

This folder contains application related configurations in a file called *user-delete.conf*

**domain**

This directory contains a file called *Even.scala* which is used to declare methods to get specific keys out of JSON.

**functions**

This folder contains the file *UserDeleteFunction.scala* which helps in processing and deleting user information from the MongoDB.

**task**

This folder contains a file called *UserDeleteStreamTask.scala* which is an entry point for this service. and another file called *UserDeleteConfig.scala* which holds the variable constants.

**resources \[test]**

This folder contains test related configurations values in a file called *test.conf*.  

**fixture**

This directory contains a file called *EventFixture* which is  a hard coded kafka events for the testing purpose. Also contains *LoadMongoData* file which holds the Mongo Data for the testing purpose.

**spec**

In the spec folder we have the main test case file called *UserDeleteFunctionTestSpec.scala* that is used to test our stream processing task.

### **Source code**

{% embed url="<https://github.com/Sunbird-Lern/data-pipeline/tree/release-7.0.0/ml-jobs/ml-user-delete>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://lern.sunbird.org/use/developer-guide/ml-service/data-pipeline-flink-jobs/ml-user-delete/folder-structure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.