> The field annotation @TableField  function is the same as [Mybatis-Plus](https://github.com/baomidou/mybatis-plus)(Hereafter referred to as MP), but compared to MP, some low-frequency use functions have been castrated. Follow-up based on user feedback can be gradually added with the iteration. The current version currently only supports the following two scenarios: 
> 
> 1. The field in the entity class is not the actual field in ES. For example, the entity class is directly used as DTO, and some extraneous fields that do not exist in ES are added. At this time, this field can be marked so that the EE framework can skip this Field, this field is not processed.
> 1. The update strategy of the field, for example, when the update interface is called, the field of the entity class is not updated until it is not Null or a non-empty string. At this time, you can add field annotations and mark the update strategy for the specified field.

Example of use:
```java
    public class Document {
    // Other fields are omitted here... 
        
    // Scenario 1: mark fields that do not exist in es
    @TableField(exist = false)
    private String notExistsField;
        
    // Scenario 2: When updating, the non-empty string in this field will be updated
    @TableField(strategy = FieldStrategy.NOT_EMPTY)
    private String creator;
    }
```
> **Tips:**
> - There are 3 types of update strategies:
>    - NOT_NULL: Non-Null judgment, only when the field value is non-Null, it will be updated
>    - NOT_EMPTY: non-empty judgment, will be updated only when the field value is a non-empty string
>    - IGNORE: Ignore the judgment, no matter what the field value is, it will be updated
> - Priority: The update strategy specified in the field annotations> the update strategy specified in the global configuration