We are looking to use the 'soft commit' feature in Solr4 to support near real time search for our production application on Heroku.
Does Websolr on Heroku support Solr4?
If yes, is it possible to use the sunspot rails gem to play nicely with a Websolr Solr4 instance.
Yes, and yes. Solr4 will become the default in Websolr sometime in March/April 2014, but for now you have to log into the Websolr control panel to create your Solr4 instance... the addon won't do it itself. If you need help navigating, please fill out a ticket on http://help.websolr.com, and someone can help you.
Related
everyone. I've been following in Github the progression of this issue handling. I think and believe all is OK now. I just need you to tell me what to do in my deployments. I've just installed Clickhouse 21.8.9, and I'm trying to make some tests in order to extract from MongoDB and fill out an aggregatingMergeTree table in Clickhouse. I've been reading a lot of tech doc about Clickhouse possibilities, so I know that is not the only way to accomplish what I want to do. But it's a valid way, so I want to test it. My Clickhouse installation comes from downloaded DEB files (I'm using Ubuntu 20.04 in my laptop). According to some changes I saw in the Clickhouse repo at Github, it seems I might have to re-compile Clickhouse, is that correct? What do you advice me to do? Thanks in advance.
PS: I've just tried in a MongoDB 3.6 and a MongoDB 4.0, the outcome is the same: no admit empty username or cannot authenticate if I use credentials
I couldn't find the add new redis database options in GoLand IDE,thanks you very mush.
enter image description here
Native Redis support is not implemented yet. Feel free to follow DBE-283.
As for now there are some third-party plugins in Marketplace to connect Redis from GoLand, please find the most suitable for you, e.g., this one.
Native Redis support is implemented now:
https://www.jetbrains.com/go/whatsnew/#databases
I am trying to install cloudant on my vulcan based app.
However when I try to add the free version of cloudant through the heroku addons I get the following error:
Could not communicate with vendor, please try again later
Want to confirm if this is a temporary vendor issue or is it something with my app?
I contacted Heroku support and was told Heroku is in the process of removing the add-on. I don't know any further details, but it looks like in order to have Cloudant work on Heroku you'll need to set the account up yourself.
This sounds like an error in the brokering between Heroku and Cloudant. If you can file a ticket with support#cloudant.com (including account information and time of the failure) we can track it down on our side and see if there's action we can take. Alternatively, you can always signup directly at cloudant.com as a short-term work around.
Is it possible to attach addons to a standalone postgres database created at https://postgres.heroku.com ? I'm using the dev plan.
The database details page # https://postgres.heroku.com/databases/ shows "Heroku PG-Backups addon not attached" under Snapshots heading. I couldn't find a way to add the PG-Backups addon.
You probably need to take a look at the docs: https://devcenter.heroku.com/articles/pgbackups#provisioning-the-add-on
I am able to replicate local and remote databases using the CouchDB replication feature. However, if I specify the source to be a secure URL (e.g. https://www.mysecurehost.com) CouchDB returns a 500 error. I am able to successfully replicate if I specify the target to be a secure URL). I am using CouchDB V1.0.2. Any help regarding this matter would be greatly appreciated.
According to Cloudant support,
CouchDB (including version 1.0.1) has
trouble with HTTPS replication. If you
can, try replicating with plain HTTP.
Otherwise you’ll have to wait until
CouchDB 1.1 is released (ETA early
2011).
They reference bug COUCHDB-491 ("Support replication over SSL"), which appears to be closed, but not actually fixed.
Update: According to Cloudant, the problem is still present if you're using a version of Erlang older than R14.
The current CouchDB release 1.0.2 fixes these issues.