Skip to content

Confusion about Mongoid integration #1005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jspawar opened this issue Sep 1, 2021 · 0 comments
Closed

Confusion about Mongoid integration #1005

jspawar opened this issue Sep 1, 2021 · 0 comments

Comments

@jspawar
Copy link

jspawar commented Sep 1, 2021

Looking at the READMEs and the example doesn't make it very clear how exactly the Mongoid integration works. So I have the following few questions to hopefully disambiguate what's going on:

  1. What do I configure for the Mongoid client's MongoDB URI? Do I still need to run a separate MongoDB instance and point it at that or do I somehow point it at an Elasticsearch instance?
    • If I do point it at an Elasticsearch instance, say a simple one running on the default 9200 port, do I just point it at like elastic-host:9200?
  2. If I have some classes that I don't care to have elastic capabilities but still need to be persisted, is that even possible? If so, how? (i.e. can I just not include the mixin or is there some configuration I need to do)

At the heart of this I guess I'm mostly wondering does using this gem somehow use Elasticsearch as a MongoDB implementation when you use it with Mongoid or is it just supplementary somehow?

Thanks.

@jspawar jspawar closed this as completed Nov 19, 2021
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

No branches or pull requests

1 participant