You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm curious about custom search support plans.
I found that it's supposed to be supported but isn't implemented yet: openmetadata-docs/content/v1.3.x/main-concepts/metadata-standard/schemas/entity/services/connections/search/customSearchConnection.md
The problem for us is that we cannot use elasticsearch, it's disabled by the company policy. We are able to use Azure cognitive search instead. If a customization in OM worked we could implement the client for it. I'm interested if there is a smooth way w/o hacking the core to replace elasticsearch with our custom one.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm curious about custom search support plans.
I found that it's supposed to be supported but isn't implemented yet: openmetadata-docs/content/v1.3.x/main-concepts/metadata-standard/schemas/entity/services/connections/search/customSearchConnection.md
The problem for us is that we cannot use elasticsearch, it's disabled by the company policy. We are able to use Azure cognitive search instead. If a customization in OM worked we could implement the client for it. I'm interested if there is a smooth way w/o hacking the core to replace elasticsearch with our custom one.
Beta Was this translation helpful? Give feedback.
All reactions