monstache
a go daemon that syncs MongoDB to Elasticsearch in realtime. you know, for search.
MIT License
Bot releases are hidden (Show)
Published by rwynn about 5 years ago
- Fix regression in last release where array values were sent to Elasticsearch with nulls prepended
- Fix issue where requests to the /instance endpoint would timeout if the process when from active to inactive in a cluster
Published by rwynn about 5 years ago
- Add GET /instance endpoint to http server for process information and status
- Fix issue where empty array sent to Elasticsearch as null instead of empty array
- Use $currentDate operator to update timestamp in cluster mode instead of process system time
- Ensure deprecated _type field is not set on all delete requests for Elasticsearch 7
Published by rwynn about 5 years ago
- Add GET /instance endpoint to http server for process information and status
- Fix issue where empty array sent to Elasticsearch as null instead of empty array
- Use $currentDate operator to update timestamp in cluster mode instead of process system time
Published by rwynn about 5 years ago
- Add GET /instance endpoint to http server for process information and status
- Fix issue where empty array sent to Elasticsearch as null instead of empty array
- Use $currentDate operator to update timestamp in cluster mode instead of process system time
Published by rwynn about 5 years ago
- Add GET /instance endpoint to http server for process information and status
- Fix issue where empty array sent to Elasticsearch as null instead of empty array
- Use $currentDate operator to update timestamp in cluster mode instead of process system time
Published by rwynn about 5 years ago
- Upgrade MongoDB go driver to 1.1.1
- Upgrade Elasticsearch go driver to 7.0.6
- Log driver versions at startup
Published by rwynn about 5 years ago
- Upgrade MongoDB go driver to 1.1.1
- Upgrade Elasticsearch go driver to 6.2.23
- Log driver versions at startup
Published by rwynn about 5 years ago
- Maintenance release for the 4.x series
- Improved decimal128 support
Published by rwynn about 5 years ago
- Maintenance release for the 3.x series
- Improved decimal128 support
Published by rwynn about 5 years ago
- Upgrade MongoDB go driver to 1.1.0 for improved performance, reliability and support for MongoDB 4.2
- Improvements to the
replayoption
Published by rwynn about 5 years ago
- Upgrade MongoDB go driver to 1.1.0 for improved performance, reliability and support for MongoDB 4.2
- Improvements to the
replayoption
Published by rwynn over 5 years ago
- Suppress logging of version conflict as an error since this is expected behavior when events are replayed
- Fix JSON serialization of Decimal128 fields
Published by rwynn over 5 years ago
- Suppress logging of version conflict as an error since this is expected behavior when events are replayed
- Fix JSON serialization of Decimal128 fields
Published by rwynn over 5 years ago
- Suppress logging of version conflict as an error since this is expected behavior when events are replayed
Published by rwynn over 5 years ago
- Suppress logging of version conflict as an error since this is expected behavior when events are replayed
Published by rwynn over 5 years ago
- Reliability improvements for direct reads of large collections
- Add
direct-read-no-timeoutoption to allow setting a no cursor timeout flag on direct reads. Fix to allow setting this option in the config file. - Ensure elasticsearch-validate-pem-file is true by default
- New feature: dynamic direct reads. Set
direct-read-namespacesto a list with a single empty string and monstache will automatically detect collections to sync in your deployment. If you have many collections you may need to use thedirect-read-concuroption to limit how many run at the same time. - Added a new option
direct-read-dynamic-exclude-regexto set a regular expression which filters out any matching namespaces from dynamic direct reads.
Published by rwynn over 5 years ago
- Reliability improvements for direct reads of large collections
- Add
direct-read-no-timeoutoption to allow setting a no cursor timeout flag on direct reads. Fix to allow setting this option in the config file. - Ensure elasticsearch-validate-pem-file is true by default
- New feature: dynamic direct reads. Set
direct-read-namespacesto a list with a single empty string and monstache will automatically detect collections to sync in your deployment. If you have many collections you may need to use thedirect-read-concuroption to limit how many run at the same time. - Added a new option
direct-read-dynamic-exclude-regexto set a regular expression which filters out any matching namespaces from dynamic direct reads.
Published by rwynn over 5 years ago
- Reliability improvements for direct reads of large collections
- Add
direct-read-no-timeoutoption to allow setting a no cursor timeout flag on direct reads - Ensure elasticsearch-validate-pem-file is true by default
Published by rwynn over 5 years ago
- Reliability improvements for direct reads of large collections
- Add
direct-read-no-timeoutoption to allow setting a no cursor timeout flag on direct reads - Ensure elasticsearch-validate-pem-file is true by default
Published by rwynn over 5 years ago
- Added new boolean option
direct-read-no-timeoutwhich when enabled sets the no cursor timeout flag on direct reads. Disabling the cursor timeout is not recommended unless an error like 'Error performing direct read of collection db.col: (CursorNotFound) ' is preventing direct reads to complete. - Known issues: the
direct-read-no-timeoutoption will only work as a command line flag. When put in the config file it has no effect. This issue will be fixed in the next release.
