Projects tigase _server tigase-mongodb Issues #14
Update MongoDB driver (#14)
Closed
Andrzej Wójcik (Tigase) opened 9 years ago
Due Date
2016-03-20

Currently we use Java driver for MongoDB in version 2.12.3 which supports MongoDB up to version 2.6 (which is rather old).

We need to update Java driver for MongoDB to version 2.14 for Tigase XMPP Server version 7.1.0 as it is latest stable version for MongoDB which support newest MongoDB 3.2 and contains old driver API.

For Tigase XMPP Server version 7.2.0 we should update driver to version 3.2 - latest version, but contains new API which could be useful as new API contains asyncronous access to MongoDB.

Andrzej Wójcik (Tigase) commented 9 years ago

%kobit Do you agree with this changes?

Artur Hefczyc commented 9 years ago

I would go for driver version 3.2 right away, if it compatible with MongoDB we are using in version 7.1.0. If not, then go ahead and do as you suggest.

Andrzej Wójcik (Tigase) commented 9 years ago

Driver API in version 3.2 was changed so I think to use driver 3.2 for Tigase XMPP Server 7.2.0 (as usage of driver 3.2 may need unknown amount of changes in our code due to changed API), and use 2.14 for 7.1 as there will be less changes and as I suppose we want to release 7.1 rather sooner than later.

Artur Hefczyc commented 9 years ago

Yes, I agree. I thought that maybe 3.2 driver version, even though it has some API changes is still backward compatible. If not, I agree with your suggested path of upgrades. Please proceed.

Andrzej Wójcik (Tigase) commented 9 years ago

I've created subtasks:

  1. Task #3950 for Tigase XMPP Server 7.1 to update to version 2.14.1

  2. Task #3951 for Tigase XMPP Server 7.2 to update to version 3.2 or newer (with API change)

Changed target version to match greatest one from subtasks.

Andrzej Wójcik (Tigase) commented 8 years ago

Upgrade of drivers for MongoDB is finished.

issue 1 of 1
Type
Task
Priority
Normal
Assignee
RedmineID
3947
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/tigase-mongodb#14
Please wait...
Page is in error, reload to recover