I would appreciate any help from the couchdb community.
Thanks.
--
Eng.º Diogo Júnior
Researcher | RD Department
Fraunhofer Portugal AICOS
Edifício Central Rua Alfredo Allen, 455/461
4200-135 Porto Portugal
How to find us
Phone: +351 22 0408 300
www: www.fraunhofer.pt
Not at present but results are returned, by default, in highest-to-lowest score
order. How are you determining that 0.1 is too low anyway?
B.
On 7 Apr 2014, at 21:25, Hank Knight hknight...@gmail.com wrote:
Is there a way to limit couchdb-lucene results so that only results
with a score of
Hi all,
I have just seen a very intersting issue which I do not fullly understand.
I have serverA and serverB, with the same replicated database db1.
Sometimes replication is just turned off. Currently it is off.
I have taken a look at a bunch of documents.and I have found a couple of
them
Jan wrote a new blog post for us:
https://blogs.apache.org/couchdb/entry/the_little_things_1_do
CouchDB takes data storage extremely seriously. This usually means we
work hard to make sure that the underlying storage modules are as
robust as we can make them. Sometimes though, we go all the
Hi,
I have found the cause of the difference in the content: my libraries are
correcting some documents when reading from couchdb (to account for missing
properties in wrongly-structured documents). Some of those corrections are
using random-generated values, and that is why I am seeing a
I’ll answer anyway.
Yes, it’s deterministic. The same document with the same history will have the
same _rev value. This is an optimization over the previous algorithm where _rev
was a random UUID. This changed years ago.
The advantage is that two servers receiving the same update can more
Ok, but does mean it is indeed related to the document content, so a
different content would produce a different revision number. In my case I
was having the same rev but different content, which is what I could not
understand (as explained, it was caused by my personal libraries)
And just
On Apr 8, 2014, at 7:31 AM, Daniel Gonzalez gonva...@gonvaled.com wrote:
Ok, but does mean it is indeed related to the document content, so a
different content would produce a different revision number.
Yes. It’s an MD5 (?) digest computed from the document JSON.
And just curious: what does
On Tue, Apr 8, 2014 at 7:01 PM, Jens Alfke j...@couchbase.com wrote:
On Apr 8, 2014, at 7:31 AM, Daniel Gonzalez gonva...@gonvaled.com wrote:
Ok, but does mean it is indeed related to the document content, so a
different content would produce a different revision number.
Yes. It’s an MD5 (?)
Dear CouchDB community,
You may or may not have heard about the Heartbleed SSL/TLS Vulnerability yet
(http://heartbleed.com). Without much exaggeration, this is a big one.
What does this mean for CouchDB?
1. If you are using CouchDB with the built-in SSL support, you are at the whim
of
Holy wow, thanks for the heads up and explanations.
On Tue, Apr 8, 2014 at 10:53 AM, Jan Lehnardt j...@apache.org wrote:
Dear CouchDB community,
You may or may not have heard about the Heartbleed SSL/TLS Vulnerability
yet (http://heartbleed.com). Without much exaggeration, this is a big
proactive to the point information when it's crucial = great service
thanks lot!
Am 08.04.2014 17:53 schrieb Jan Lehnardt j...@apache.org:
Dear CouchDB community,
You may or may not have heard about the Heartbleed SSL/TLS Vulnerability
yet (http://heartbleed.com). Without much exaggeration,
Yup I almost mentioned PouchDB when I seen this thread come up, from an
external implementors perspective it isnt great that CouchDB uses the
internal erlang binary term format to create revisions, its possible to
implement it compatibly but decided against it due to extra deps +
complexity
From
by not conflicting the users loses information
By not conflicting, do you mean two docs with different content having same
rev? How is this possible? I thought the original poster on this thread
said he was wrong about that.
On Tue, Apr 8, 2014 at 4:56 PM, Dale Harvey d...@arandomurl.com
On 27 October 2013 14:44, Jens Alfke j...@couchbase.com wrote:
On Oct 26, 2013, at 3:05 PM, Chad Cross chadcr...@gmail.com wrote:
Essentially, a standard data set for CRUD-type applications.
There's the beer database that comes with Couchbase Server; I have a
CouchDB-compatible copy of it
15 matches
Mail list logo
