o worries, that's common with containers.If if you're still
> concerned about memory here is one recent issue discussing a few
> strategies how to introspect it and possible reduce it a bit:
> https://github.com/apache/couchdb/discussions/4992
>
> Cheers,
> -Nick
>
> On Wed, May 1, 2024 a
correction, just realised it's a container doh... host is Debian, container
(official image) is using 1.5GB
> On 1 May 2024, at 22:17, TDAS wrote:
>
> Hey all
>
> I have an instance of CouchDB that's taking 1.5GB of RAM when it's not really
> doing much at all. A
Hey all
I have an instance of CouchDB that's taking 1.5GB of RAM when it's not really
doing much at all. About 10k docs, one replication, that's about it... any
suggestions where I can start looking - version is v3.3.3, running on Debian.
Thanks!
Is there an efficient way of using a stored function within views, without
having the function redeclared for every document that’s parsed?
EG if it was possible to declare a function outside the doc parser:
const matcher = ({name, title}) => {/* do stuff here */}
const formatter = ({info}) =>
table/api/ddoc/search.html#get--db-_design-ddoc-_search-index
>
> You might mean ?include_fields=["createdDate"] ?
>
> B.
>
>> On 12 Nov 2023, at 19:12, TDAS wrote:
>>
>> …thinking further on this, can I return a number of fields with the index
>
…thinking further on this, can I return a number of fields with the index that
aren’t searched? EG if I have a ‘doc.createdDate’, how can I just return that
with the data?
> On 12 Nov 2023, at 18:19, TDAS wrote:
>
> Basically, I was hoping that I could have the search query return
You can't fetch another document during the indexing callbacks.
>
> Perhaps explain what you're trying to achieve?
>
> \b.
>
>> On 11 Nov 2023, at 23:54, TDAS wrote:
>>
>> getDoc doesn’t exist? Did chatgpt just make that up?! Man…
>>
>> Is there an
not to be indexed at all.
>
> B.
>
>> On 11 Nov 2023, at 17:30, TDAS wrote:
>>
>> Hey all
>>
>> I have Clouseau running, and have written a search index which is working
>> nicely.
>>
>> However when I try to link a document, the sear
Hey all
I have Clouseau running, and have written a search index which is working
nicely.
However when I try to link a document, the search stops returning any results.
I’ve checked it with chatgpt (so it must be right, hey!) :)
Can anyone point out what I’m doing wrong?
The doc.owner is
That’s really odd, they’re booleans in fauxton… not sure what happened there...
> On 14 Sep 2023, at 14:47, Robert Newson wrote:
>
> Hi,
>
> It's true not 'true' (boolean not string).
>
> B.
>
>> On 13 Sep 2023, at 22:54, TDAS wrote:
>>
>> Ok
]
}
This is my index:
function (doc) {
if (doc.type === 'user' && doc.firstname && doc.lastname) {
index('name', doc.firstname + ' ' + doc.lastname, { 'store': 'true' });
index('firstname', doc.firstname, { 'store': 'true' });
}
}
> On 13 Sep 2023, at 22:06, TDAS wro
need to
> choose which adapter you'd like.
>
> The next major release of couchdb will include an alternative Lucene indexing
> system that works with Java 11 through 20 and will include the Java artifacts
> necessary to run the whole stack.
>
> B.
>
>> On 13 Sep 202
Greetings
I’ve set up an index in a design doc, and I’m trying to use _search after a
long wait I get:
{
"error": "ou_est_clouseau”,
"reason": "Could not connect to the Clouseau Java service at
clouseau@127.0.0.1”
}
So, I’ve been looking into installing this but am
I’ve migrated couchdb over to a new server, using replication. Latest couchdb
running on Debian 11.
Everything is working except ‘find’ (using Nano, from a NodeJs app).
It’s a long time since I set the search tree up, but essentially it looks like
the below (if of interest) - I can’t really
14 matches
Mail list logo
