| *** vnaboychenko has quit IRC | 02:14 | |
| *** crxz0193 has joined #magnetodb | 03:12 | |
| *** setho has joined #magnetodb | 07:09 | |
| setho | hello guys! | 07:10 |
|---|---|---|
| isviridov | setho hi | 07:17 |
| isviridov | setho I 've found really good Irc client for Android Andchat you have to try | 07:21 |
| setho | Andchat? thanks! | 07:36 |
| achuprin | hello guys! | 07:43 |
| *** jeromatron has joined #magnetodb | 07:43 | |
| achuprin | isviridov: What Irc client do you use on Linux? | 07:44 |
| *** idegtiarov has joined #magnetodb | 08:31 | |
| pas-ha | achuprin: hexchat is nice GUI client | 08:51 |
| *** ominakov has joined #magnetodb | 09:06 | |
| ominakov | hello | 09:07 |
| aostapenko | hello | 09:15 |
| miarmak | hi guys | 09:25 |
| *** miarmak has quit IRC | 09:26 | |
| *** pas-ha has quit IRC | 09:26 | |
| *** pas-ha has joined #magnetodb | 09:26 | |
| achuprin | pas-ha: tahnks | 09:28 |
| *** miarmak has joined #magnetodb | 09:31 | |
| *** achuprin_ has joined #magnetodb | 09:34 | |
| *** achuprin has quit IRC | 09:34 | |
| isviridov | achuprin_: it is konversation and irssi | 09:54 |
| *** pas-ha has quit IRC | 10:08 | |
| *** pas-ha has joined #magnetodb | 10:09 | |
| miarmak | isviridov, dukhlov, achudnovets: a new bug has been reported https://bugs.launchpad.net/magnetodb/+bug/1302459 | 10:15 |
| *** pas-ha has quit IRC | 10:15 | |
| *** pas-ha has joined #magnetodb | 10:18 | |
| isviridov | miarmak, not a bug | 10:30 |
| miarmak | isviridov: why not? | 10:30 |
| isviridov | miarmak, 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 API | 10:38 |
| isviridov | miarmak, next step we will add async tasks execution, so any uncontrolled DB changes could corrupt data | 10:39 |
| isviridov | miarmak, just don't do it :) | 10:40 |
| miarmak | isviridov: but we don't have delete table in api yet =) | 10:41 |
| *** jeromatron has quit IRC | 10:43 | |
| *** achuprin has joined #magnetodb | 10:44 | |
| achudnovets | isviridov: this bug can be reproduced using API | 10:46 |
| *** achuprin_ has quit IRC | 10:46 | |
| achudnovets | 1) create table in non existing keyspace | 10:46 |
| achudnovets | 2) it's fails . Create keyspace | 10:46 |
| achudnovets | 3) create table again. | 10:47 |
| achudnovets | and it's fails | 10:47 |
| achudnovets | with TableAlreadyExists error | 10:47 |
| achudnovets | but there is no table in Cassandra | 10:47 |
| isviridov | miarmak, yeap. It is a real problem. Charles Wang is working on it https://blueprints.launchpad.net/magnetodb/+spec/os-restful-api-delete-table | 10:48 |
| miarmak | isviridov: look at achudnovets's message | 10:50 |
| miarmak | isviridov: he has had the same problem today | 10:50 |
| isviridov | achudnovets, it is another scenario and it looks like reported https://bugs.launchpad.net/magnetodb/+bug/1295077 | 10:51 |
| isviridov | miarmak, achudnovets does it affect you? | 10:54 |
| miarmak | isviridov: a little) yesterday I had a problem with testing data-load script | 10:55 |
| achudnovets | isviridov: 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 cassandra | 10:55 |
| isviridov | achudnovets, please report a bug | 10:55 |
| achudnovets | isviridov: ok | 10:56 |
| openstackgerrit | A change was merged to stackforge/magnetodb: Added CentOS support https://review.openstack.org/84758 | 10:56 |
| *** ominakov has quit IRC | 11:00 | |
| * isviridov @ meeting | 11:02 | |
| *** ominakov has joined #magnetodb | 11:03 | |
| *** jeromatron has joined #magnetodb | 11:12 | |
| achudnovets | isviridov: bug report about table creation. https://bugs.launchpad.net/magnetodb/+bug/1302495 with my comment | 11:12 |
| isviridov | achudnovets, awesome! I've reviewed and set low prior | 11:20 |
| *** jeromatron has quit IRC | 11:28 | |
| *** ominakov has quit IRC | 11:42 | |
| *** ominakov has joined #magnetodb | 11:45 | |
| *** ominakov has quit IRC | 11:49 | |
| *** ominakov has joined #magnetodb | 11:52 | |
| *** dmakogon_ is now known as denis_makogon | 12:14 | |
| *** crxz0193 has quit IRC | 12:30 | |
| *** ominakov has quit IRC | 12:33 | |
| *** ominakov has joined #magnetodb | 12:39 | |
| *** jeromatron has joined #magnetodb | 13:03 | |
| *** ominakov has quit IRC | 13:31 | |
| *** jeromatron has quit IRC | 13:31 | |
| *** ominakov has joined #magnetodb | 13:32 | |
| *** achuprin has quit IRC | 13:43 | |
| *** achuprin_ has joined #magnetodb | 13:43 | |
| *** Keith_ has joined #magnetodb | 14:10 | |
| aostapenko | guys, 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 25 | 14: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 performance | 14:12 |
| Keith_ | not sure if it 25 is the perfect number | 14: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 deployment | 14:13 |
| isviridov | Keith_, yes. It should be blueprinted | 14:24 |
| isviridov | aostapenko, currently it is not implemented, so can't be tested | 14:24 |
| aostapenko | isviridov, Keith_: thank you | 14:29 |
| achudnovets | isviridov: 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 |
| isviridov | achudnovets, it can be one of ways and I like it. But there is a trap to create bug for unexisting functionality. | 14:32 |
| isviridov | achudnovets, f.e. we have request validation. And any missed case can be reported as bug | 14:33 |
| isviridov | achudnovets, 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 |
| achudnovets | isviridov: 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 |
| isviridov | achudnovets, let us start with one. With workitems we can track it. | 14:44 |
| achudnovets | ok, let's try | 14:47 |
| *** jeromatron has joined #magnetodb | 15:01 | |
| *** idegtiarov has quit IRC | 15:11 | |
| *** pas-ha has quit IRC | 15:20 | |
| *** jeromatron has quit IRC | 16:13 | |
| *** dukhlov__ has quit IRC | 16:27 | |
| achudnovets | bye guys | 16:39 |
| *** achudnovets has left #magnetodb | 16:39 | |
| *** setho has quit IRC | 16:40 | |
| *** dukhlov__ has joined #magnetodb | 16:43 | |
| *** ominakov has quit IRC | 16:54 | |
| aostapenko | bye | 16:55 |
| *** aostapenko has left #magnetodb | 16:55 | |
| *** jeromatron has joined #magnetodb | 16:59 | |
| miarmak | bye fellows! have a nice weekend! | 17:10 |
| *** miarmak has quit IRC | 17:10 | |
| *** jeromatron has quit IRC | 17:12 | |
| dukhlov__ | bye guys | 17:17 |
| *** jeromatron has joined #magnetodb | 17:26 | |
| *** openstackgerrit has quit IRC | 18:01 | |
| *** openstackgerrit has joined #magnetodb | 18:02 | |
| *** denis_makogon has quit IRC | 18:19 | |
| *** dmakogon_ has joined #magnetodb | 18:19 | |
| *** jeromatron has quit IRC | 20:04 | |
| *** jeromatron has joined #magnetodb | 20:48 | |
| *** jeromatron has quit IRC | 20:53 | |
| *** jeromatron has joined #magnetodb | 21:06 | |
| *** [o__o] has left #magnetodb | 21:20 | |
| *** [o__o] has joined #magnetodb | 21:23 | |
| *** Keith_ has quit IRC | 22:08 | |
| *** jeromatron has quit IRC | 22:23 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!