Friday, 2014-04-04

*** vnaboychenko has quit IRC02:14
*** crxz0193 has joined #magnetodb03:12
*** setho has joined #magnetodb07:09
sethohello guys!07:10
isviridovsetho hi07:17
isviridovsetho I 've found really good Irc client for Android Andchat you have to try07:21
sethoAndchat? thanks!07:36
achuprinhello guys!07:43
*** jeromatron has joined #magnetodb07:43
achuprinisviridov: What Irc client do you use on Linux?07:44
*** idegtiarov has joined #magnetodb08:31
pas-haachuprin: hexchat is nice GUI client08:51
*** ominakov has joined #magnetodb09:06
miarmakhi guys09:25
*** miarmak has quit IRC09:26
*** pas-ha has quit IRC09:26
*** pas-ha has joined #magnetodb09:26
achuprinpas-ha: tahnks09:28
*** miarmak has joined #magnetodb09:31
*** achuprin_ has joined #magnetodb09:34
*** achuprin has quit IRC09:34
isviridovachuprin_: it is konversation and irssi09:54
*** pas-ha has quit IRC10:08
*** pas-ha has joined #magnetodb10:09
miarmakisviridov, dukhlov, achudnovets: a new bug  has been reported
*** pas-ha has quit IRC10:15
*** pas-ha has joined #magnetodb10:18
isviridovmiarmak, not a bug10:30
miarmakisviridov: why not?10:30
isviridovmiarmak, you are actually corrupting DB and expecting proper working. The table is not only one place where mdb table is mentioned. But anyhow it is not a usecase, everything should be done via API10:38
isviridovmiarmak, next step we will add async tasks execution, so any uncontrolled DB changes could corrupt data10:39
isviridovmiarmak, just don't do it :)10:40
miarmakisviridov: but we don't have delete table in api yet =)10:41
*** jeromatron has quit IRC10:43
*** achuprin has joined #magnetodb10:44
achudnovetsisviridov: this bug can be reproduced using API10:46
*** achuprin_ has quit IRC10:46
achudnovets1) create table in non existing keyspace10:46
achudnovets2) it's fails . Create keyspace10:46
achudnovets3) create table again.10:47
achudnovetsand it's fails10:47
achudnovetswith TableAlreadyExists error10:47
achudnovetsbut there is no table in Cassandra10:47
isviridovmiarmak, yeap. It is a real problem. Charles Wang is working on it
miarmakisviridov: look at achudnovets's message10:50
miarmakisviridov: he has had the same problem today10:50
isviridovachudnovets, it is another scenario and it looks like reported
isviridovmiarmak, achudnovets does it affect you?10:54
miarmakisviridov: a little) yesterday I had a problem with testing data-load script10:55
achudnovetsisviridov: I think it's two separate bugs. First is bug with nonexistent keyspace. Second is bug with nonexistent tables. I believe it is connected with new tbale schema in cassandra10:55
isviridovachudnovets, please report a bug10:55
achudnovetsisviridov: ok10:56
openstackgerritA change was merged to stackforge/magnetodb: Added CentOS support
*** ominakov has quit IRC11:00
* isviridov @ meeting11:02
*** ominakov has joined #magnetodb11:03
*** jeromatron has joined #magnetodb11:12
achudnovetsisviridov: bug report about table creation. with my comment11:12
isviridovachudnovets, awesome! I've reviewed and set low prior11:20
*** jeromatron has quit IRC11:28
*** ominakov has quit IRC11:42
*** ominakov has joined #magnetodb11:45
*** ominakov has quit IRC11:49
*** ominakov has joined #magnetodb11:52
*** dmakogon_ is now known as denis_makogon12:14
*** crxz0193 has quit IRC12:30
*** ominakov has quit IRC12:33
*** ominakov has joined #magnetodb12:39
*** jeromatron has joined #magnetodb13:03
*** ominakov has quit IRC13:31
*** jeromatron has quit IRC13:31
*** ominakov has joined #magnetodb13:32
*** achuprin has quit IRC13:43
*** achuprin_ has joined #magnetodb13:43
*** Keith_ has joined #magnetodb14:10
aostapenkoguys, should we allow batch write to process more than 25 put/delete requests in ReST API? Now it cat process more than 25, but DynamoDB docs says than there is a restriction for 2514:10
Keith_there does need to be a limit, since a batch request that is too large can tie up connections and threads and affect overall performance14:12
Keith_not sure if it 25 is the perfect number14:12
Keith_i'd implement it to be configurable, and return a "request too large" if it's larger than what's configured.  then the number can be configured based on the size of the deployment14:13
isviridovKeith_, yes. It should be blueprinted14:24
isviridovaostapenko, currently it is not implemented, so can't be tested14:24
aostapenkoisviridov, Keith_: thank you14:29
achudnovetsisviridov: MagnetoDB currently lacks validation checks. May be the best to report a bug for missed checks? Bug report should contain request example and expected response. Then will be quite easy to write a unit tests and implement missed code.14:29
isviridovachudnovets, it can be one of ways and I like it. But there is a trap to create bug for unexisting functionality.14:32
isviridovachudnovets, f.e. we have request validation. And any missed case can be reported as bug14:33
isviridovachudnovets, but we don't have functionality for checking requests for size (close to network infrastructure) and request amount (close to quota). So blueprint is the best for such ideas.14:35
achudnovetsisviridov: ok. I agree. btw as I know we currently have no restrictions for request size, item length, etc. Implementation of such things is trivial, but there are lot of such things :). So we need a lot of bps or bug reports for this. One general bp for restriction implementation may work, but developer can easily miss something. And one bp is hard to parallelize...14:42
isviridovachudnovets, let us start with one. With workitems we can track it.14:44
achudnovetsok, let's try14:47
*** jeromatron has joined #magnetodb15:01
*** idegtiarov has quit IRC15:11
*** pas-ha has quit IRC15:20
*** jeromatron has quit IRC16:13
*** dukhlov__ has quit IRC16:27
achudnovetsbye guys16:39
*** achudnovets has left #magnetodb16:39
*** setho has quit IRC16:40
*** dukhlov__ has joined #magnetodb16:43
*** ominakov has quit IRC16:54
*** aostapenko has left #magnetodb16:55
*** jeromatron has joined #magnetodb16:59
miarmakbye fellows! have a nice weekend!17:10
*** miarmak has quit IRC17:10
*** jeromatron has quit IRC17:12
dukhlov__bye guys17:17
*** jeromatron has joined #magnetodb17:26
*** openstackgerrit has quit IRC18:01
*** openstackgerrit has joined #magnetodb18:02
*** denis_makogon has quit IRC18:19
*** dmakogon_ has joined #magnetodb18:19
*** jeromatron has quit IRC20:04
*** jeromatron has joined #magnetodb20:48
*** jeromatron has quit IRC20:53
*** jeromatron has joined #magnetodb21:06
*** [o__o] has left #magnetodb21:20
*** [o__o] has joined #magnetodb21:23
*** Keith_ has quit IRC22:08
*** jeromatron has quit IRC22:23

Generated by 2.14.0 by Marius Gedminas - find it at!