Shorting the prefix to something like j1 was one work around but this does go against the spirit of our project - each developer has their own stack instead of sharing the same MIE insights.
Are you aware of any other possible work arounds/fixes/hacks? Or are we looking at bitting the bullet and sharing a MIE stack?
p.s. I really do appreciate your support @aburkleaux-amazon :)
I've released version 2.0.0 of Content Analysis on Github: https://github.com/awslabs/aws-content-analysis/releases/tag/v2.0.0
This release includes big back-end changes but very few UX/UI changes. Most notably, MIE has been decoupled from Content Analysis, thus greatly improving code maintainability.
Afternoon @ianwow - have a quick question about a PR you recently merged in (ref: aws-solutions/aws-media-insights-engine#635). We're looking at 'Restarting' a failed job and noticed they would always pass through and get marked as completed. After tracking it down we realised you have already fixed it (coincidental timing huh 😅)
Our question is - would the fix be able to be merged into v3 of MIE and released? I did notice it would technical be a 'breaking change' as the new field is referenced in exchange for old behaviour. Could this be mitigated against by checking for the new 'MediaType' key and if not present default to old behaviour. Something to this effect:
media_type = retrieve_asset["results"]["MediaType"] if "MediaType" in retrieve_asset["results"] else s3key.split('.')[-1]
Hope I managed to explain our problem enough, if not please feel free to say and I'll try and expand more 🙂
Hey folks, was wondering what the thought were on having the ability to set the MaxAttempts, Backoff Rate & Interval Seconds as parameters to allow operators to retry more then twice.
We've seem to of hit a rate limit (in this case sentiment analysis via a custom operator) which being able to back off a few more times with retries would give us a better fighting chance on it going through