Comments for David Cassel

Comment on Splitting data with Info Studio by Geert

Geert — Tue, 24 Jan 2012 12:43:08 +0000

Actually, derived documents do should be inserted into the current Database (which is Fab) to enable the information studio to do its book keeping properly. In order to do this book keeping properly you should replicate the info: document properties, overriding the info:source-location one with a value pointing to the current one. You should also copy the collection. This allows the unload feature to also include these derived documents.

Another way is to split inside the collector. There are some good examples here: https://github.com/marklogic/infostudio-plugins

Comment on Sneak Peak: ImageMagick in MarkLogic by Norman Walsh

Norman Walsh — Tue, 17 Jan 2012 16:54:51 +0000

FWIW, I added support for this to the DocBook XSLT 2.0 stylesheets a while back. If you’re running them on MarkLogic 5 with ImageMagick support, the ImageMagick functions are used to compute the dimensions of embedded images.

Comment on CurioVault: putting the Express License to work by Dave

Dave — Sat, 07 Jan 2012 22:27:33 +0000

Nice work Dave

Comment on Models in XQuery by MicahLogic : Micah Dubinko | Blog Archive | Resurgence of MVC in XQuery

Thu, 08 Dec 2011 21:27:36 +0000

[...] been an increasing amount of talk about MVC in XQuery, notably David Cassel’s great discussion and to an extent Kurt Cagle’s platform discussion that touched on forms interfaces. Lots of [...]

Comment on MarkLogic on $40 per month by Dave Cassel

Dave Cassel — Wed, 30 Nov 2011 04:27:43 +0000

Shannon, you are correct on the 2-CPU limit. The Amazon EC2 Large instance has "4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each)". Scroll to Measuring Compute Resources on the instance types page for a description of EC2 Compute Units. For licensing purposes, MarkLogic measures cores, but the EC2 Large only has 2 cores, so it still works. The server will definitely be happier with the extra RAM (7.5 GB for Large, 1.7 GB for Small).

Comment on MarkLogic on $40 per month by Shannon Scott Shiflett

Shannon Scott Shiflett — Tue, 29 Nov 2011 23:34:12 +0000

Davids,

The CPU restriction does not exclude the “large” instance option, then?

My understanding is, there is a 2-CPU limit, but each CPU is permitted multiple cores, is that right?

Thanks for the post and discussion,
Shannon

Comment on MarkLogic on $40 per month by Dave Cassel

Dave Cassel — Thu, 24 Nov 2011 15:22:43 +0000

Thanks for the information, David. Applying the same math to the Large instance ($910/year plus $0.12/hour for a reserved instance) it looks like the max EC2 charge is about $163.43/month.

Comment on MarkLogic on $40 per month by David Lee

David Lee — Wed, 23 Nov 2011 20:46:41 +0000

I have installed 5.0 using the Express license on a EC2 “large” instance which gives 8GB of RAM. I’m not sure how well ML will perform on a small instance, but its worth a try.

The Large instance performs quite well with the exception that EBS volumes, being a fancy kind of NAS can be slow to get going as the data has to be network copied to the local server, and back to the NAS for writes.

Generally though I suggest this is a great way to get started with MarkLogic with minimal initial investment.

Comment on Element constructors: computed and direct by Dave Cassel

Dave Cassel — Mon, 21 Nov 2011 19:17:24 +0000

Good point, Evan. I’ve done that mixed approach accidentally before (trying to include a value, but getting the whole attribute instead), but I don’t tend to think of doing it that way on purpose.

Comment on Element constructors: computed and direct by Evan Lenz

Evan Lenz — Mon, 21 Nov 2011 19:12:52 +0000

Nice post, Dave. Note you also have the option of using a computed attribute constructor with a direct element constructor. So your conditional attribute example could be simplified like this:

{ if ($condition) then attribute simple { “true” } else () }

In general, I think it’s a good practice to avoid computed constructors except in the cases you describe. Direct constructors are much more readable, like you said.