Lars, Andrew, Michael,
This particular discussion isn't bearing fruit for the user@hbase audience.
If you wish to continue it, especially with the current tone, please do so
on dev@.
Michael, IANAL but the ASF offers indemnification as a means of encouraging
development and adoption of the
Trying to figure out the best place to jump in here...
Kristoffer,
I would like to echo what Michael and Andrew have said. While a
pre-aggregation co-proc may work in my experience with co-procs they are
typically more trouble than they are worth. I would first try this outside
the client
Yes, the tone is a problem here, but the good news is rectally induced
hypoxia isn't a real medical condition, a patch seems possible, social
grace isn't required for producing a patch, and patches are always welcome.
What else is there to say, really? I think we're done.
On Saturday, April 11,
Well Lars, looks like that hypoxia has set in…
If you’ve paid attention, its not that I’m against server side extensibility.
Its how its been implemented which is a bit brain dead.
I suggest you think more about why having end user code running in the same JVM
as the RS is not a good thing.
2 things u need:
1st: if zookeeper is not managed by hbase (i.e u start zookeeper as separate
process), then hbase-env.sh must have entry :
export HBASE_MANAGES_ZK=false
2nd: remove all entries that starts with 127. in /etc/hosts
