Commited changes to allow a client to automatically refresh stale schema during certain ops.

0 views
Skip to first unread message

Sanjit Jhala

unread,
Aug 17, 2009, 1:39:50 PM8/17/09
to hypertable-...@googlegroups.com
Commited changes to allow a client to automatically refresh stale schema during 
certain ops.

-Allows clients to be transparently deal with non-conflicting schema changes
during table mutations and certain hql commands
-Refresh cached schema on a client get_schema call
-Added regression test for changes
http://github.com/sjhalaz/hypertable/commit/45219966f231658755441cd58a74f0f4d844ae4f

-Sanjit

Luke

unread,
Aug 17, 2009, 2:34:52 PM8/17/09
to hypertable-...@googlegroups.com
I suggest that we set a small refresh limit instead of using
while(true), to avoid accidental ddos on hyperspace.

Sanjit Jhala

unread,
Oct 2, 2009, 6:28:55 PM10/2/09
to hypertable-...@googlegroups.com
-Allows clients to be transparently deal with non-conflicting schema changes
during table mutations and certain hql commands
-Refresh cached schema on a client get_schema call
-Added regression test for changes

http://github.com/sjhalaz/hypertable/commit/86dcd78076037f6d0c946ea882e7ab957755cc02

-Sanjit

Luke

unread,
Oct 2, 2009, 7:36:11 PM10/2/09
to hypertable-...@googlegroups.com
HT_THROW2 should be used (see the note for line 380) to preserve the
exception chain.

Sanjit Jhala

unread,
Oct 4, 2009, 2:19:39 PM10/4/09
to hypertable-...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages