Nelson Elhage

There's no option to do so, currently. You could force it to skip by populating the `mosql_tailers` table, which is where MoSQL stores its current progress. We do have a...

Yeah, that seems plausible. I'd probably make it a CLI flag, `--limit` or something. I'd also consider `--query` or `--filter` that only applies to the initial import and takes a...

Your input document has > "tags"=>"[]" i.e. it looks like the value is the stringified form of a JSON array. MoSQL expects `ARRAY` columns to be actual BSON arrays in...

`4fa0c49bc43e9e0700000085` is the record in your pasted logs I was looking at -- what do you get if you try the same check on that `_id`?

The high-level picture is simple: You will need to discover each of the backing shards, and tail them individually, tracking state separately. The thorny issue comes around chunk migrations by...

One option is, for each record in postgres, to keep track (in an additional column, managed entirely by MoSQL) of which shards it exists in. An insert appends to that...

I haven't heard of anyone doing so, although I'd be happy to take a PR. The logic should probably go in or around `transform` in `lib/mosql/schema.rb`. We use `COPY FROM`...

Yeah, I definitely like the idea of having pluggable transformers for columns. It's something I've thought about, but haven't gotten time to implement, so I'd be happy to review a...

That's a reasonable optimization. It's also vaguely on my list to try to optimize `$set` ops to not need to read the original record in from Mongo, and just translate...

If you run an import with `-v`, it should show some basic stats about where the time is spent -- in SQL vs. reading/transforming the data. What does that show?...