Reserved JSON Words in 2.0?
I know it says "there are no reserved field names" when I create a document, but I'm having trouble with "Vendor Name". I made a simple view without any if statements to emit one record per document:
function (doc, meta) {
emit(
[
'hi'
], {
'foo': 'bar'
});
}
If my document (testing::123) looks like this:
{
"click": "to edit",
"new in 2.0": "there are no reserved field names",
"Vendor Name": "There Might Be One"
}
I can see it in the Documents tab, but nothing is emitted from the view. If I change "Vendor Name" to "Vendor Names", 1 row is emitted from the view. Has anyone else run into this? Is there a list of reserved fields somewhere?
Thanks,
-Eric
PS I'm running Version: 2.0.0 enterprise edition (build-1976).
Thanks for trying to recreate it. After reading your message I made a new Data Bucket and tried reproducing my own results and wasn't able to. I'm only able to reproduce it on the "Default" bucket. Strange stuff. In the end, I'm building a system that isn't going to use a "Default" bucket so it's technically a non-issue.
My setup is 4 Windows Server 2008 virtual boxes (stop laughing) using VMware. As for my logs, I only see a bunch of "node x noticed node y went up/down". I'll need to figure that out too but that's a separate conversation.
Thanks again for trying to reproduce it.
Hello,
I have tested with my installation (on Mac and and Linux) and I cannot reproduce this.
On which OS are you running? anything in the log?
Regards
Tug
@tgrall