Status Update
Comments
ma...@delvedeeper.com <ma...@delvedeeper.com> #2
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
va...@google.com <va...@google.com>
nr...@google.com <nr...@google.com> #3
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
mi...@delvedeeper.com <mi...@delvedeeper.com> #4
Thanks for the quick reply.
Service Configs affected by the issue are generating >$1M of incremental revenue yearly for our client, and the fact that this issue is resurfacing yet another time or so is leading our Client to question the reliability of Google Cloud infrastructure and putting at risk client's budgets planned for spending on Google Cloud.
Looking forward to getting more information from you soon!
Best regards
M.
nr...@google.com <nr...@google.com> #5
Hello,
Thank you for contacting the Google Cloud support team.
To ensure a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking
Please note that the Issue Tracker is primarily meant for reporting commonly observed issues and requesting new features. For individual support issues, it is best to utilize the support ticketing system.
We appreciate your cooperation!
ma...@delvedeeper.com <ma...@delvedeeper.com> #6
The issue is very urgent
ma...@delvedeeper.com <ma...@delvedeeper.com> #7
Filters are not working correctly and the prediction request returns products that don't meet the filtering criteria. It keeps breaking and fixing itself every month without any changes on our end.
When can you resolve it?
Description
When running predictions with filters, the filters are being ignored and incorrect products are returned.
"filter": "tag=(\"promo1\" OR \"promo2\" OR \"promo3\") filterOutOfStockItems"
What you expected to happen:
Return only products with promo1 or promo2 or promo3.
Actual results attached.
Steps to reproduce:
from googleapiclient.discovery import build
from oauth2client.service_account import ServiceAccountCredentials
client = build(
'retail',
'v2',
discoveryServiceUrl='
credentials=credentials
)
PROJECT_ID = 'xxxxxxxxxxxxxxxxxxxxxxx'
SERVING_CONFIG_ID = 'xxxxxxxxxxxxxxxxxxxxxxx'
endpoint = f'projects/{PROJECT_ID}/locations/global/catalogs/default_catalog/servingConfigs/{SERVING_CONFIG_ID}'
if __name__ == '__main__':
ids = ['xxxxxxxxxxxxxxxxxxxxxxx', 'xxxxxxxxxxxxxxxxxxxxxxx', 'xxxxxxxxxxxxxxxxxxxxxxx']
response_list = []
for id in ids:
request = {
"userEvent": {
"eventType": "home-page-view",
"visitorId": id
},
"filter": "tag=(\"promo1\" OR \"promo2\" OR \"promo3\") filterOutOfStockItems",
"params": {
"strictFiltering": True
}
}
print(request)
response = client.projects().locations().catalogs().servingConfigs().predict(
placement=endpoint,
body=request
).execute()
results = response['results']
response_list.extend([item['id'] if 'id' in item else item for item in results])
print(set(response_list))
Other information (workarounds you have tried, documentation consulted, etc):
1) different options for strictFiltering
2)