Skip to content

Ispn 1797 Implement MongoDB based cache store#1473

Closed
gscheibel wants to merge 1 commit intoinfinispan:masterfrom
gscheibel:ISPN-1797
Closed

Ispn 1797 Implement MongoDB based cache store#1473
gscheibel wants to merge 1 commit intoinfinispan:masterfrom
gscheibel:ISPN-1797

Conversation

@gscheibel
Copy link
Copy Markdown
Contributor

No description provided.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where exactly ? the capital S in the "CacheStore" word

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/MongoBD/MongoDB/

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ohh yes, I read it 3 times and didn't see the typo :)

@Sanne
Copy link
Copy Markdown
Member

Sanne commented Jan 14, 2013

Hi @gscheibel , great steps forward! This looks like almost ready.

Could you rebase this all and squash it in a single commit? As I have some minor comments to do yet but it's hard to find where to comment exactly.

Then to be really perfectionist, these are the things I'd love you to check:

  • I think to have noticed some mixing of tabs and whitespace formatting. I'm not sure it might be an illusion from mis-formatted class: see for example the constructor of MongoDBCacheStoreConfig
  • there are changes in the root pom.xml of Infinispan which I don't think should be part of this patch. Maybe it's just whitespace changes?
  • MongoDBConfigurationParser has some IDE generated comments left over
  • Could you remove the log4j.properties file?

Could you write up a couple of paragraphs in the Infinispan documentation about how to use it, maybe with an example configuration if you think that could help?

@gscheibel
Copy link
Copy Markdown
Contributor Author

@Sanne I've just perform the code style reformat and the squash, now I get started on the doc

@gscheibel
Copy link
Copy Markdown
Contributor Author

@Sanne I was about to start the documentation on Confluence when I saw an email from Manik about a refactoring of the doc (probably moving to ascii doc). I think I should probably wait the new way of documenting instead of working on Confluence and then have to move to the new way.
WDYT ?

@Sanne
Copy link
Copy Markdown
Member

Sanne commented Jan 25, 2013

It would be great to have it in Confluence first as otherwise it will be delayed a lot. We'll be able to export from Confluence to ascii doc, so hopefully it will only requires some minor style / formatting.

Looking forward for the docs :)

@gscheibel
Copy link
Copy Markdown
Contributor Author

@Sanne I don't have the right to add a page into the user guide. Which "workflow" should I follow, I submit a page doc to the team and someone will integrate it ? Should I ask someone (who ?) ?

@Sanne
Copy link
Copy Markdown
Member

Sanne commented Feb 7, 2013

@gscheibel this would be a great time to finally merge this in Infinispan: 5.2 was released and 5.3 will start release train very soon.
Will you have time to rebase this, change the pom to 5.3.0-SNAPSHOT and address Davide's comments?
We could then finally make clustered queries to work for OGM/MongoDB

@gscheibel
Copy link
Copy Markdown
Contributor Author

@Sanne done. I have mainly refactored the exception management. WDYT ? (cc @DavideD)

parent/pom.xml Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see OGM is using version 2.9.0 . Could we use the same?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The latest version is 2.10.1.
In 2.10.0 they have added a new MongoClient class which replace the Mongo class. By default, the new one connects to the server with a WriteConcern at ACKNOWLEGEMENT. https://jira.mongodb.org/browse/JAVA-682
So should I implement this version (and in OGM as well ?)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right in that case I think we should upgrade OGM too, also people will be happy that we will use the same WriteConcern as the driver by default: less confusing.
You choose if you have time to fix OGM first, for me it mostly important that we can keep using the same versions across this module and OGM, or we won't be able to use them together as we'd like to. Of course we won't always be able to keep them perfectly in sync but since you say they changed the API this looks like an urgent concern. Could you start by opening an OGM issue?

/cc @emmanuelbernard

@gscheibel
Copy link
Copy Markdown
Contributor Author

@Sanne to activate the mongodb module you need to have MONGODB_HOSTNAME defined just like for OGM.
The safemode option doesn't exist anymore so you won't find it in the configruation section.
All tests are passing with version 2.0.2, 2.0.7 and 2.2.3 of the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants