Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Mon, 4 Mar 2013 14:21:14 +0000 (UTC)
From: "Jan Lehnardt (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12544309.1330374817659.375219.1362406874702@arcas>
In-Reply-To: <JIRA.12544309.1330374817659@arcas>
References: <JIRA.12544309.1330374817659@arcas>
Subject: [jira] [Commented] (COUCHDB-1425) Emitting UTF-8 chars >= 0xD800 in
 JS map stops design doc from indexing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592226#comment-13592226 ] 

Jan Lehnardt commented on COUCHDB-1425:
---------------------------------------

Commit / Branch here: https://git-wip-us.apache.org/repos/asf/couchdb/repo?p=couchdb.git;a=commit;h=be4e41ff27a9c5ac270e24dcf2b3fca26a938149

+1 on landing this in 1.3.1 and 1.4.0.


> Emitting UTF-8 chars >= 0xD800 in JS map stops design doc from indexing
> -----------------------------------------------------------------------
>
>                 Key: COUCHDB-1425
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1425
>             Project: CouchDB
>          Issue Type: Bug
>          Components: JavaScript View Server
>    Affects Versions: 1.1.1
>         Environment: Mac OS 10.6.8, but not sure that matters.
>            Reporter: Jim Klo
>         Attachments: utf8.c.diff
>
>
> Was trying determine UTF-8 Char collation, using the following Gist: https://gist.github.com/1904807
> It turns out that once the view gets to the document that would emit "\uD800", the view server times out and stops indexing that design document.
> This seems like a bug, since I can 'store' a document with UTF-8 chars >= 0xD800, but one cannot emit a key with that char in the string.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira