-
-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Custom Search Attributes to TemporalNamespace #567
Comments
+1 This would be a very useful feature. |
Hi @dmytro-orlenko ! Good idea! Are you interested on contributing for this feature? |
@alexandrevilain Really appreciate your efforts in addressing the issues!! I think it would be really convenient to be able to add custom search attributes via the TemporalNamespace manifest. Thanks. |
@alexandrevilain I'm not sure about my changes, can you help me with it? #602 |
Hi @dmytro-orlenko ! Thanks for your contribution. According to the temporal documentation about search attributes, the command to use is: After a quick look at the cli's codebase, we can find the code handling this in the cli, see: https://github.com/temporalio/cli/blob/main/searchattribute/search_attribute_commands.go#L62 Looks like the search attribute reconciliation should be done in another step, after the namespace has been created :) Hope it helps. |
It looks more complicated than I thought |
I can help you implementing this @dmytro-orlenko :) |
fyi @alexandrevilain, i'm planning to start work on this in the near term |
@alexandrevilain apologies for the delay. I've implemented custom search attributes in my fork. Based on my light manual testing, looks like it works 😄. The only thing that's making me hesitate to make the PR is some more testing. Will do more manual testing tomorrow, and will probably need to write some code test in wdyt? |
Cool @TheHiddenLayer ! Thanks for your work! Feel free to open a Draft pull request ;) |
Custom Search Attributes as a part of namespace and can help to search workflow by attributes
The text was updated successfully, but these errors were encountered: