> For the complete documentation index, see [llms.txt](https://portal-integracao.intelbras.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portal-integracao.intelbras.com.br/linha-android/iaserver/aifacefeatureqbicproxy-obsoleto.md).

# AiFaceFeatureQbicProxy (obsoleto)

O recurso facial valoriza a classe de operação do banco de dados de cache de memória para 1:N quando o rosto reconhecimento.

Nota: O valor do recurso facial é carregado na lógica da memória tanto quanto possível quando o processo inicia a execução assíncrona, geralmente não precisa parar, todo o ciclo de vida e o ciclo de vida do processo é consistente, porque a necessidade de monitorar a memória do valor da característica nominal banco de dados de cache é um erro anormal, erro anormal ao ser recarregado característica persistente valor na memória, caso contrário, levará a informações persistentes do banco de dados, mas pode não reconhecimento do problema do sucesso.

Geralmente, a parte que acessa não precisa gerenciar o banco de dados de cache. Se for um projeto customizado e não suporta plataforma para emissão de face, o negócio precisa gerencie o banco de dados de cache sozinho, caso contrário, a comparação não poderá ser bem-sucedida. Específico pode ser determinado de acordo com o projeto.

```java
/**
* qbic algorithm abnormal callback interface
*/
public interface FaceFeatureQbicListener {
    
/**
* qbic algorithm abnormal callback interface
* Please see detailed error type {@ link com. Lamy. SDK. Aiserver. AiServerErrorType}
*
* @param errorType error type
*/
void onError(int errorType);

}
/**
* Set face feature value memory QBIC database monitor
*
* @param listener listener
*/
public void setQbicListener(FaceFeatureQbicListener listener);

/**
* Startup algorithm
*
* @return Execution result
*/
public boolean start();

/**
* Stop algorithm
*
* @return Execution result
*/
public boolean stop();

/**
* Create a face database
*
* @return Execution result
*/
public int createFeatureDB();

/**
* Add the feature value of featureObjId into the database
*
* @param featureObj feature data
* @param featureObjId feature id (generally the face Id in the persistent database), the Id will be
returned to the access party after face comparison, for the access party to query the corresponding
face information from the persistent database
* @return Execution result
*/
public int insertFeature(byte[] featureObj, int featureObjId);

/**
* Update the feature value of featureObjId in the database
*
* @param featureObj feature data
* @param featureObjId feature id (generally the face Id in the persistent database), the Id will be
returned to the access party after face comparison, for the access party to query the corresponding
face information from the persistent database
* @return Execution result
*/
public int updateFeature(byte[] featureObj, int featureObjId);

/**
* Delete the feature value of featureObjId from the database
*
* @param featureObjId feature id
* @return Execution result
*/
public int deleteFeature(int featureObjId);

/**
* Destroy face characteristic value database, after destruction, face comparison can not be successful
* Usually no call is required
*
* @return Execution result
*/
public int destroyFeatureDB();


```


---

# 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://portal-integracao.intelbras.com.br/linha-android/iaserver/aifacefeatureqbicproxy-obsoleto.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.