Skip to main content

· One min read
botlikes456

Watchmen V16.1 series, is planning to stop to maintain in few weeks after V16.3 deployed.

We have done refactoring in V16.2, which leads the package structure break changes. In detail, we extract the common part from 4 supported rds storage (MySQL/MSSQL/Oracle/PostgreSQL) to a new package watchment-storage-rds. This change reduce our maintain cost on rds part, but on the other hand, because of lacking of manpower resource, it's really hard to maintain V16.1 since it still in original structure. Anyway, V16.1 is still on maintain now, but it's better to do upgrading to V16.2 now.

One more thing about V16.3, after we deploy the indicator workbench in V16.2, there is one more exciting feature will be deployed in V16.3, which is Synonym Topic. It introduces direct link to rds, to reuse the existing tables and views, to maximize the existing data usages. We are still on the final round verification work now, will be released in few weeks ❤️‍🔥.

· One min read
botlikes456

V16.2 coming soon!

V16.2 is coming in next few days, including amazing features,

  • AWS S3 and Ali OSS supporting for raw topic storage,
  • PostgreSQL supporting,
  • Indicator workbench, offers buckets, indicators, inspections, etc.

· One min read
botlikes456

Watchmen V15 series, which deployed about 2 months ago, and was the very first version we published, working with us over 1 year, we decide stop to maintain, and will not fix bug in this version again.

We already notify all our friends to upgrade their images to V16.1.x, and get good feedback from them. So if you still on V15 series, we highly recommend to upgrade to V16.1 immediately.

We offer upgrade scripts, you can find it at watchmen-migration , just enjoy it.

Still, images of V15 series can be found at,

· One min read
The Watchmen Team

V16.1.1 Released!

It is patch release, which contains bugfixes.

Bugfixes​

  • Remove exception raise from ask encryptor from registration
  • Flatten column is not working
  • DataSourceParam is unserializable
  • Bad argument passed of post_delete_pipeline
  • Missing the precision cell of factor in uploaded template