4 ms·
I read this as HipChat’s own export function having problems handling large amounts of data. I’m not sure how this is Mattermost’s fault.
by lvillani 8y ago
I read this as HipChat’s own export function having problems handling large amounts of data.
I’m not sure how this is Mattermost’s fault.
- Karunamon 8y agoI'm not sure what they mean by "export function". Hipchat isn't "an application", it's a bunch of services running on a network of VMs. At the very least, Hipchat includes Elasticsearch and MySQL. Seems odd that they'd rely on any particular Hipchat API when they can rip that data out of the guts of the machine.
- slinkyavenger 8y agoI'm sure there's a fair amount of business logic between what's in the database and what's delivered to the presentation layer. Pulling from a database means that the new company has to reverse engineer Hipchat's API implementation.
- solatic 8y agoHipChat internally uses Postgres and Redis, not some proprietary undocumented blob store. While I'm sure that a working applicative export function would make things easier, I don't see why you can't give Mattermost the relevant read-only credentials to those datastores and let Mattermost read directly from the source.