IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:

• According to the documentation Method: projects.locations.operations.list lists operations that match the specified filter in the request.
• In the Query parameters section is mentioned that the filter key and value should be specified as key=value; nevertheless, no matter the filter specified the API always return all the operations.
• Here an example used:

curl \
  'https://translation.googleapis.com/v3/projects/54864101xxxx/locations/us-central1/operations?filter=state%3DRUNNING&key=[YOUR_API_KEY]' \
  --header 'Authorization: Bearer [YOUR_ACCESS_TOKEN]' \
  --header 'Accept: application/json' \
  --compressed

• The API responded with all the operations instead of only filter the ones in RUNNING state.
• Same happens when using Python code with many permutations of the filter, including "done!=true", "status!=done", "metadata.state!=SUCCEEDED", "metadata.state=FAILED", etc. It doesn't matter what puts in for a key/value pair, always get every operation.

How this might work:

• The API should respond with only filtered operation in RUNNING state (or any other state specified) instead of all the operations.
• Specify in the documentation how to filter this operations in python such as key/value pair and the format accepted to do this.

If applicable, reasons why alternative solutions are not sufficient:

• Is it required to filter operations according to its state.