Couchbase Server

Documentation outdated in page http://www.couchbase.com/docs/couchbase-devguide-2.0/filter-extract-data.html

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta, 2.0-beta-2, 2.0
  • Fix Version/s: 2.0
  • Component/s: documentation
  • Security Level: Public
  • Labels:
    None

Description

The page at:

http://www.couchbase.com/docs/couchbase-devguide-2.0/filter-extract-data.html

Shows several documents with the _id and _rev fields. These meta data fields are no longer inlined in documents after DP4.

Also, the field "language" for design documents has no special meaning in Couchbase (unlike Apache CouchDB), being superfluous and confusing to users.

There's also a map function example with duplicated if conditional:

function(doc) {
if (doc.title) {
   if(doc.title) {
     emit(doc.title, null);
   }
  }
}

Finally, the following paragraph:

"As a best practice we want make sure that the fields we want to include in our index actually exist. Therefore we have our map function within a conditional: if (doc.age && doc.name). This ensures the fields exist in documents when we query the view and we therefore avoid a view failure when Couchbase Server generates the index."

Is not completely correct. If doc.age or doc.name don't exist in a document, using them as keys or values doesn't produce an error.
Undefined fields in JavaScript are serialized to a JSON null value.
What would produce an error would be something like referencing doc.name.length, when name isn't defined in the document.

Activity

Ascending order - Click to sort in descending order
MC Brown made changes -
Field Original Value New Value
Assignee MC Brown [ mccouch ] Karen Zeller [ kzeller ]
Farshid Ghods made changes -
Fix Version/s 2.0 [ 10114 ]
Hide
Permalink
Karen Zeller added a comment -
Ok. I've updated the paragraph to say:

    <para>
      Here is how the map function appears when you provide full
      handling of all JSON document information:
    </para>

<programlisting>
function (doc, meta) {
  if (meta.type == "json" &amp;&amp; doc.title &amp;&amp; doc.date) {
    // Check if doc is JSON
    emit(doc.title, doc.date);
  } else {
    // do something with binary value
  }
}
</programlisting>
  
   <para> As a best practice we want make sure that the fields we want to emit in our index
   actually exist before we emit it to the index. Therefore we have our map function within a
   conditional: <literal>if (doc.title &amp;&amp; doc.date)</literal>. For instance,
   if we wanted to perform a views function
   that tried to reference <literal>doc.name.length</literal> we would get a null value if the
   field does not exist and the view function would fail. By checking for the field we avoid
   these potential types of errors.</para>


This will be available here later today: http://www.couchbase.com/docs/couchbase-devguide-2.0/filter-extract-data.html
Show
Karen Zeller added a comment - Ok. I've updated the paragraph to say:     <para>       Here is how the map function appears when you provide full       handling of all JSON document information:     </para> <programlisting> function (doc, meta) {   if (meta.type == "json" &amp;&amp; doc.title &amp;&amp; doc.date) {     // Check if doc is JSON     emit(doc.title, doc.date);   } else {     // do something with binary value   } } </programlisting>       <para> As a best practice we want make sure that the fields we want to emit in our index    actually exist before we emit it to the index. Therefore we have our map function within a    conditional: <literal>if (doc.title &amp;&amp; doc.date)</literal>. For instance,    if we wanted to perform a views function    that tried to reference <literal>doc.name.length</literal> we would get a null value if the    field does not exist and the view function would fail. By checking for the field we avoid    these potential types of errors.</para> This will be available here later today: http://www.couchbase.com/docs/couchbase-devguide-2.0/filter-extract-data.html
Hide
Permalink
Karen Zeller added a comment -
See updated text/example.
Show
Karen Zeller added a comment - See updated text/example.
Karen Zeller made changes -
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Karen Zeller made changes -
Status Resolved [ 5 ] Closed [ 6 ]
Hide
Permalink
Filipe Manana added a comment -
Karen, Thanks.

However this part:

For instance,
   if we wanted to perform a views function
   that tried to reference <literal>doc.name.length</literal> we would get a null value if the
   field does not exist and the view function would fail. By checking for the field we avoid
   these potential types of errors.</para>

Is still not correct. For that example (doc.name.length) we would not get null, but rather an "undefined reference" exception would be raised by the JavaScript engine. Doing "doc.name" is what would produce a null.

Show
Filipe Manana added a comment - Karen, Thanks. However this part: For instance,    if we wanted to perform a views function    that tried to reference <literal>doc.name.length</literal> we would get a null value if the    field does not exist and the view function would fail. By checking for the field we avoid    these potential types of errors.</para> Is still not correct. For that example (doc.name.length) we would not get null, but rather an "undefined reference" exception would be raised by the JavaScript engine. Doing "doc.name" is what would produce a null.
Hide
Permalink
Filipe Manana added a comment -
See comment above.
Show
Filipe Manana added a comment - See comment above.
Filipe Manana made changes -
Resolution Fixed [ 1 ]
Status Closed [ 6 ] Reopened [ 4 ]
Hide
Permalink
Karen Zeller added a comment -
I see, and will add this information. In the future for these types of issues, it would be more helpful if you not only call out the error, but also explain what happens to server behavior (does it crash, does it freeze, is it unable to handle other views in the design document, etc. and if there is a solution/workaround) This is truly the important information for customers/customer support not just errorname=XYZ appears.....


Thanks!
Show
Karen Zeller added a comment - I see, and will add this information. In the future for these types of issues, it would be more helpful if you not only call out the error, but also explain what happens to server behavior (does it crash, does it freeze, is it unable to handle other views in the design document, etc. and if there is a solution/workaround) This is truly the important information for customers/customer support not just errorname=XYZ appears..... Thanks!
Karen Zeller made changes -
Status Reopened [ 4 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Karen Zeller made changes -
Status Resolved [ 5 ] Closed [ 6 ]
Hide
Permalink
Filipe Manana added a comment -
Karen, I said what it happens, the JavaScript function will raise an exception.

As described in the wiki and other places, when that happens a log message is logged to mapreduce_errors.N file, referencing the error, document ID, bucket name, design document name, etc. This doesn't crash or freezes the server.
Show
Filipe Manana added a comment - Karen, I said what it happens, the JavaScript function will raise an exception. As described in the wiki and other places, when that happens a log message is logged to mapreduce_errors.N file, referencing the error, document ID, bucket name, design document name, etc. This doesn't crash or freezes the server.

People

  • Assignee:
    Karen Zeller
    Reporter:
    Filipe Manana
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: