Hi all,
Here is the PR for the prometheus endpoint:
https://github.com/apache/couchdb/pull/3416. Would love to get some eyes on
it.
Thanks,
Tony
On Tue, Sep 29, 2020 at 8:52 AM Mike Rhodes wrote:
> For me, I think Bob's approach below, combined with ensuring the overhead
> of coding the en
Hi all,
I recently started implementing _active_tasks for our fdb development
branch. At first, I thought it would be trivial, but technical limitations
have led me to modify our response as an interim solution. I'd like to get
more feedback on this solution and start a discussion on a more
acc
Hello Everyone,
Will and I were hoping to get some more opinions for
https://github.com/apache/couchdb/pull/962.
To provide some context, Mango had a long existing bug that allowed users
to incorrectly use an index for a query. This bug was fixed in
https://github.com/apache/couchdb/pull/816. How
t other possibilities are there?
>
> We could set a max recursion depth, perhaps.
>
> couchjs has a limit on max stack size; a recursion depth limit would be
> similar in spirit.
>
> If nothing else is possible I'm happy for this change as a last-ditch
> effo
Hi all,
In mango, once a user has correctly setup text search, he or she can create
a simple text index with:
{
"type" : "text"
"index" :{}
}
This default basically indexes every field in a document for the entire db.
Unfortunately, for large dbs, this is resource intensive. Even with
warnings,
Hey Teo,
Were you able to get Mango text search working? Specifying the analyzer
get's a little tricky.
On Sat, Jul 30, 2016 at 5:17 AM, Constantin Teodorescu
wrote:
> Is Mango Full text indexer/search (or would it be) immune for accented
> letters?
>
> I'm planning to use it for searching "
Feature: Fauxton, Garren Smith
> >
> > Week 2
> > Aug 1: The CouchDB 2.0 Architecture, Robert Newson
>
> Robert tells me that he’s not gonna make Aug 1. Can somebody trade?
>
> Best
> Jan
> --
>
> > Aug 3: Feature: Mango query, Tony Sun
> >
>
Hi Jenn,
I can volunteer for the mango blog. I won't be able to do it for next
week, but should have some free time to write something after that.
Thanks,
Tony
On Tue, Jul 19, 2016 at 3:16 PM, Reddy B. wrote:
> Hi Jenn,
>
> Just to share two topics ideas for the Migration Guide :
>
> - it
Hi Robert,
Building upon what others have stated above, what do you think about
the following:
1) Let the user query without creating an index
2) Return an error message with a new url that has
"slow/no_index/developer":true appended at the end. The message clearly
explains that this
Hi all,
Hope everyone enjoyed the holidays!
This is the most common mango experience for new users:
1) Syntax issues to create an index.
2) Running into the "no index found" error because his or her query
(with and w/o sort) doesn't match the index correctly.
3) We explain ho
[
https://issues.apache.org/jira/browse/COUCHDB-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Sun resolved COUCHDB-2651.
---
Resolution: Fixed
> Deleting a Mango Design Docs using bulk d
[
https://issues.apache.org/jira/browse/COUCHDB-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Sun resolved COUCHDB-2645.
---
Resolution: Fixed
> Mango should return the created design
[
https://issues.apache.org/jira/browse/COUCHDB-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Sun resolved COUCHDB-2622.
---
Resolution: Fixed
> Comparison function returns boolean rather than num
[
https://issues.apache.org/jira/browse/COUCHDB-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Sun resolved COUCHDB-2663.
---
Resolution: Fixed
Assignee: Tony Sun
> w:2 property in index d
[
https://issues.apache.org/jira/browse/COUCHDB-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Sun resolved COUCHDB-2614.
---
Resolution: Fixed
> Selectors with {$eq: 'foo', $gte: 'foo
[
https://issues.apache.org/jira/browse/COUCHDB-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Sun updated COUCHDB-2622:
--
Description: In mango_json:cmp/2, we call couch_ejson_compare:less_json(A,
B) which returns a boolean
Tony Sun created COUCHDB-2622:
-
Summary: Comparison function returns boolean rather than number.
Key: COUCHDB-2622
URL: https://issues.apache.org/jira/browse/COUCHDB-2622
Project: CouchDB
Issue
[
https://issues.apache.org/jira/browse/COUCHDB-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335844#comment-14335844
]
Tony Sun commented on COUCHDB-2614:
---
A couple of things after I noticed after
[
https://issues.apache.org/jira/browse/COUCHDB-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335514#comment-14335514
]
Tony Sun commented on COUCHDB-2614:
---
You are correct, but I think in the query a
[
https://issues.apache.org/jira/browse/COUCHDB-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Sun reassigned COUCHDB-2614:
-
Assignee: Tony Sun
> Selectors with {$eq: 'foo', $gte: 'foo
[
https://issues.apache.org/jira/browse/COUCHDB-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334303#comment-14334303
]
Tony Sun commented on COUCHDB-2614:
---
[empty] indicates an unsatisfiable range. i
21 matches
Mail list logo
