Skip to main content
Version: v1.13 print this page

Search Datasets

Note

User can disable Search Datasets & File Search in order to save some cost by reaching out to admin, Admins need to disable it.

Amorphic enables user to search any query within the dataset and metadata files. The search can be done using the search dataset feature on the home page.

The User can search for a dataset giving the name of dataset or part of it in search bar, to get it displayed in the search results. Some departments or user groups might have access to certain Datasets. User can check which Datasets you have access to as well as request access to a Dataset you do not have access.

User can type "*" in search bar to get the list of all dataset, accessible and non-accessible, in the account.

Search_Datasets

User can also view the analytics data of files matched in the dataset search results.

File analytics in search results

Customized Dataset Search (API Only)

Datasets search now has been enhanced to allow users to query (from) datasets that user has access (owner or read-only) to. To use it, following parameters have to be passed to API

Resource Path: /datasets/search
HTTP Method: GET
Query String Parameters: searchDatasets=user
Note

Other Query String Parameters like sortby, sortorder, limit etc., can be passed on along with searchDatasets.

For a Multi tenancy deployment, dataset search works a little different. Since each tenant's data is isolated and remains invisible to other tenants. Amorphic dataset search only returns the datasets which are part of user accessible tenants. Example: : If user "UserA" has access to "testorg1" and "testorg2" tenants and is searching for datasets, the search results would only display the datasets which are are under created under domains which are part of tenants "testorg1" or "testorg2"

Repair Search Metadata (API Only)

This option provides user ability to repair search metadata that is stored in the ES cluster.

Resource Path: /opensearchindex/operations
HTTP Method: PUT
Request Payload:
{
"IndexAction": <string> (recreate, delete, create)
}

User can perform below three actions:

  • recreate: Deletes and recreates index
  • delete: Deletes index
  • create: Creates index