ewencp

6 ms·

1.
by ewencp 5y ago
The downloads page is only for official releases, RCs are not distributed the same way and are not permanent unless promoted to an official release. See the mailing list thread for 2.8.0-RC0 for where to find the bits if you want to test h
2.
by ewencp 8y ago
terraform: 2014 ansible: 2012 openstack: 2010 cloudera: 2008 hortonworks: 2011 emr: 2011 (those were quickly googled, apologies if i got any dates wrong) timing is important. cloudera had good, early timing and looked promising because of i
3.
by ewencp 9y ago
Regarding your first issue, this is very much a matter of defaults. I can't be sure of your exact pipeline and connectors, but if, for example, you were using the JDBC connector, it has included support for at least prefixing names sin
4.
by ewencp 9y ago
I should also mention that system/integration tests of the new functionality was a requirement for releasing it. For example, here's one of the tests https://github.com/apache/kafka/blob/trunk/t
5.
by ewencp 9y ago
It's not Jepsen, but we actually do a fair amount of system and integration testing, some of which does things like kill nodes (randomly, the controller, etc) and validates data is delivered correctly. There is some ongoing work to add
6.
by ewencp 9y ago
Debezium implements Kafka Connectors, so the serialization is pluggable. Debezium can work with thrift, you just need a thrift converter for Kafka Connect.
7.
by ewencp 10y ago
It's not particularly efficient, but probably the easiest way to draw Voronoi diagrams on the GPU doesn't require a shader at all. Instead, use an orthographic projection and draw cones for each vertex with the cone's apex at
8.
Getting Started with Kafka in Node.js with the Confluent REST Proxy(confluent.io)
8 points by ewencp 11y ago|0 comments
9.
A Comprehensive, Open Source REST Proxy For Kafka(blog.confluent.io)
13 points by ewencp 11y ago|0 comments
10.
by ewencp 12y ago
For apt repositories, you might be interested in http://www.aptly.info/ , especially if you want to host it on S3 as it integrates very well. As others have mentioned reprepo isn't that tough to use either, but moving i
11.
by ewencp 12y ago
In particular, http://kafka.apache.org/documentation.html#intro_consumers addresses the concept of consumer groups and what ordering is guaranteed. One thing that might be worth noting for the grandparent is that Kafka cons
12.
by ewencp 12y ago
Agreed! It's not Docker, but I'm working on getting a decent Vagrant setup included with Kafka: https://issues.apache.org/jira/browse/KAFKA-1173 That supports pulling up a full cluster locally in Virtual
13.
by ewencp 12y ago
Along similar lines, all of the English Wikipedia is < 10GB, and about 45GB uncompressed: http://en.wikipedia.org/wiki/Wikipedia:Database_download#Eng... . That omits all the history (just the current pages), but sti
14.
by ewencp 13y ago
The golang folks did a nice write-up on profiling Go code: http://blog.golang.org/profiling-go-programs and it covers both CPU and heap profiling. They've incorporated Google's perftools directly with Go which mak
15.
by ewencp 13y ago
This is correct, here are the physical measurements: Nexus 4: 133.9 x 68.7 x 9.1 mm Nexus 5: 137.84 x 69.17 x 8.59 mm That said, I still find it frustrating -- the Nexus 4 screen is already too large for me to comfortably reach all parts
16.
by ewencp 13y ago
Many years later, similar functionality made it into gdb: http://sourceware.org/gdb/wiki/ReverseDebug
17.
by ewencp 13y ago
Given the huge variation in (mis)calibrated settings on top of the huge variation of displays themselves, you'd probably be fine running f.lux. In fact, I would think you would want a more flexible tool so you can actually test what di
18.
by ewencp 13y ago
Thanks for trying it out. Sounds like a bug in the collection editor. I want to improve that process to handle cases like yours -- if you don't find the feed, make it easy to look it up and add it -- but I wasn't sure that was top
19.
by ewencp 13y ago
Ah, sorry, I was using it in the locality sense (as in, coherent access). Admittedly less common, but not uncommon, in algorithms; downright confusing if you're in an architecture frame of mind.
20.
by ewencp 13y ago
I'm just learning Go, I'm certainly no evangelist. One huge difference for me, however, doesn't have to do with the language. It's deployment. It's really nice for deployment to be scp rather than a bunch of packa
21.
by ewencp 13y ago
For the vast majority of cases, I would expect panic/recover to work for iteration over in-memory data structures. For something like a database iterator where the possible errors are more varied and likely, I agree an explicit iterato
22.
by ewencp 13y ago
To build on thrownaway2424's response, the point in the article was to demonstrate the pattern for building the iterator. Very simply structured data helps do that. In reality you'd probably be iterating over a more complicated da
23.
by ewencp 13y ago
Fair enough. My day-to-day coding with Go right now involves large data sets where materializing something like that would be expensive. I'll admit my view of the issue is strongly biased by my very real need for iterators or something
24.
by ewencp 13y ago
I mentioned this pitfall, but didn't show how to solve it. I haven't seen a complete example yet and didn't take the time to work out the details yet. I'm less concerned about complexity in the iterator implementation, b
25.
by ewencp 13y ago
Testing performance by iterating over an array can be dangerous because all the data is conveniently grouped together such that the processor will have the next data it needs in cache once it's loaded the first item (most of the time;
26.
by ewencp 13y ago
I'll buy that -- it's sort of mentioned in the post as an object-based wrapper around the closure version, except I listed the functions as HasNext() and Next(). More boilerplate for the iterator implementer, but I agree, it reads
27.
by ewencp 13y ago
You need them because the examples are intentionally simplified. Even a data structure as simple as a dictionary has a useful variety of iterators: over keys, over values, and in some languages, over (key,value) tuples. Explicit iterators a
28.
by ewencp 14y ago
Should probably qualify: MBP from 3-4 years ago... But I don't expect it should suck this bad this quickly....
29.
by ewencp 14y ago
Not in my experience -- I have the same issues on my MBP, though I use it maybe 1/10th the time, so I'm less certain of that impression.
30.
by ewencp 14y ago
I honestly can't give hard numbers, but I really did switch back to FF because of the memory usage. My ancient-by-HN-standards but not-too-ancient-by-normal-standards desktop with 4GB RAM (Ubuntu 10.04 if that's relevant) was starting to th

More ›