Listing functions by filtering on metadata returns empty list

​@Anders Brakestad I tried from my end and I was able to list the functions with the relevant metadata. Can you please let me know the SDK version that you are using? Also can you try again using the latest SDK version(7.73.4)?

The missing filter parameter metadata was added to client.functions.list from SDK v7.54.1. 

Hi and thanks for the fast reply.

I was using version 7.73.3. I now upgraded to version 7.73.4 of the cognite SDK, but I still cannot list functions with metadata.

If it helps I want to list functions with 

metadata={"project": "alarm dashboard backend"}

in the “abp-dev” tenant.

I don’t have access to the project. But it retruns an empty list when the key, value pair does not match any existing function.

​@Jørgen Lund any idea regarding this issue?

​@Anders Brakestad When you’re doing 

client.functions.list(metadata={"my_key": "my_val"}, limit=None)

does the function have other key and value pairs as well? If it does, that explains why. It filters on the metadata as a whole.

Yes it does.

But why different implementation for functions and other CDF data? The expected functionality is to filter on any metadata matches. That is how we search for stuff in CDF. Matching the entire metadata dict makes no sense.

😉

Yes, I agree that it would be more useful to filter on parts of the metadata. I’ll confer with our PM about this.

​@Anders Brakestad ​@Henrik Eiding shall I convert this to a product idea?

Yes, that would be great :) Thanks!

​@Anders Brakestad Done

I’ll add my voice to this, filtering on metadata as a whole is not useful. Filtering on parts of metadata as with other resources is what we consider as expected behavior. Are this the only resource where this happens or are there other instances where the filter is on the metadata as a whole, because if so then those should also be updated to filter on parts of metadata (the key value pairs specified in the request).