Elastic Search alternative to exposing properties for reporting
Has anyone tried passing report definitions into pxRetrieveSearchData to query against Elastic Search, as opposed to the usual exposing of db columns for reporting? This would be for the purpose of avoiding exposing columns and the potential performance issues once too many columns need exposed to meet customer needs. Just trying to see if I'm in new territory here, or if this 'wheel' has already been created and proven out.
***Edited by Moderator Marissa to add SR Details***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
V7 search API (pxRetrieveSearchData) requires class and report definition name as a parameter.
List fields that are defined in report definition are returned in search results and Filters that are defined in report definition are appended to search filters.
BTW, it only works with List report(Summary/rank/etc is not supported)
Also in customer's case, they will have to create or update data transform/data instance pySearchModel to include properties that they want to retrieve in search results(retrieval of standard properties is by default supported). Any changes to pySearchModel requires full re-indexing of given class.
Last but not the least assuming customer has work class, indexing should be enabled on work class for search to work.
Keep up to date on this post and subscribe to comments
- Running Report Definition using Elastic Search Report nested property problem
- Not able to include custom properties in elastic search using the pxRetrieveSearchData- Custom elastic search
- Will elastic search work on fully exposed industry standard external tables?
- Elastic search on workobjects- finding the property that contains the search string
- Elastic Search for reporting