By default, each search result will contain very limited details — typically only the unique identities (GUID and qualifiedName) and name of each asset. This is intentional, to prevent retrieving more information than you need, as every piece of information you retrieve will add a little bit of time to the overall runtime of your request.
You can request additional details on each search result, though, to ensure the search gives you back exactly the information you require:
Start building a FluentSearch query (in this example from a client, using its 'assets' member's select() method).
Chain as many includeOnResults calls as you like. Each method call should include a searchable Atlan field you want to include on each search result. (And this can include relationship attributes as well, such as the columns in a table in this example.)
You can then run the search as you like (in this example, streaming the results directly).
Start building a FluentSearch query (in this example using its select() method directly).
Chain as many include_on_results calls as you like. Each method call should include a searchable Atlan field you want to include on each search result. (And this can include relationship attributes as well, such as the columns in a table in this example.)
You can then run the search as you like (in this example, converting to a request and running the search using the request).
Start building a FluentSearch query (in this example from a client, using its 'assets' member's select() method).
Chain as many includeOnResults calls as you like. Each method call should include a searchable Atlan field you want to include on each search result. (And this can include relationship attributes as well, such as the columns in a table in this example.)
You can then run the search as you like (in this example, streaming the results directly).
Start building a FluentSearch query (in this example from a client, using its 'assets' member's select() method).
Chain as many includeOnResults calls as you like, to include one or more relationships on each search result.
Then chain as many includeOnRelations calls as you like. Each method call should include a searchable Atlan field you want to include on each relationship included in each search result. (In this example, every related column that comes back for each search result will include the column's name.)
You can then run the search as you like (in this example, streaming the results directly).
Start building a FluentSearch query (in this example using its select() method directly).
Chain as many include_on_results calls as you like, to include one or more relationships on each search result.
Then chain as many include_on_relations calls as you like. Each method call should include a searchable Atlan field you want to include on each relationship included in each search result. (In this example, every related column that comes back for each search result will include the column's name.)
You can then run the search as you like (in this example, converting to a request and running the search using the request).
Start building a FluentSearch query (in this example from a client, using its 'assets' member's select() method).
Chain as many includeOnResults calls as you like, to include one or more relationships on each search result.
Then chain as many includeOnRelations calls as you like. Each method call should include a searchable Atlan field you want to include on each relationship included in each search result. (In this example, every related column that comes back for each search result will include the column's name.)
You can then run the search as you like (in this example, streaming the results directly).