| *** yingjun_ has joined #openstack-searchlight | 00:36 | |
| *** TravT has quit IRC | 00:49 | |
| *** bpokorny has quit IRC | 01:05 | |
| *** yingjun_ has quit IRC | 01:13 | |
| *** yingjun_ has joined #openstack-searchlight | 01:13 | |
| *** lakshmiS_ has quit IRC | 01:59 | |
| *** TravT has joined #openstack-searchlight | 02:36 | |
| *** ekarlso has quit IRC | 02:52 | |
| *** bpokorny has joined #openstack-searchlight | 02:55 | |
| *** yingjun_ has quit IRC | 02:57 | |
| *** yingjun_ has joined #openstack-searchlight | 02:57 | |
| *** yingjun_ has quit IRC | 03:01 | |
| *** TravT has quit IRC | 03:03 | |
| *** ekarlso has joined #openstack-searchlight | 03:06 | |
| *** bpokorny has quit IRC | 03:07 | |
| *** yingjun_ has joined #openstack-searchlight | 04:26 | |
| *** yingjun_ has quit IRC | 04:31 | |
| *** TravT has joined #openstack-searchlight | 04:41 | |
| *** bpokorny has joined #openstack-searchlight | 04:41 | |
| *** bpokorny has quit IRC | 05:00 | |
| *** yingjun_ has joined #openstack-searchlight | 05:29 | |
| *** yingjun_ has quit IRC | 05:38 | |
| *** TravT has quit IRC | 05:42 | |
| *** TravT has joined #openstack-searchlight | 05:45 | |
| *** TravT has quit IRC | 05:50 | |
| *** yingjun_ has joined #openstack-searchlight | 05:56 | |
| *** TravT has joined #openstack-searchlight | 06:05 | |
| *** TravT has quit IRC | 07:07 | |
| *** TravT has joined #openstack-searchlight | 07:12 | |
| *** TravT has quit IRC | 07:17 | |
| *** TravT has joined #openstack-searchlight | 07:17 | |
| *** TravT has quit IRC | 07:36 | |
| *** TravT has joined #openstack-searchlight | 07:41 | |
| *** TravT has quit IRC | 07:50 | |
| *** TravT has joined #openstack-searchlight | 07:51 | |
| *** TravT has quit IRC | 08:00 | |
| *** TravT has joined #openstack-searchlight | 08:04 | |
| *** TravT has quit IRC | 08:13 | |
| *** TravT has joined #openstack-searchlight | 08:15 | |
| *** TravT has quit IRC | 08:19 | |
| *** TravT has joined #openstack-searchlight | 08:24 | |
| *** yingjun_ has quit IRC | 08:28 | |
| *** yingjun_ has joined #openstack-searchlight | 08:29 | |
| *** TravT has quit IRC | 08:32 | |
| *** TravT has joined #openstack-searchlight | 08:38 | |
| *** TravT has quit IRC | 08:47 | |
| *** TravT has joined #openstack-searchlight | 08:52 | |
| *** TravT has quit IRC | 09:01 | |
| *** TravT has joined #openstack-searchlight | 09:02 | |
| *** TravT has quit IRC | 09:11 | |
| openstackgerrit | Li Yingjun proposed openstack/python-searchlightclient: Add resource type list CLI https://review.openstack.org/249076 | 09:11 |
|---|---|---|
| *** TravT has joined #openstack-searchlight | 09:12 | |
| *** ig0r_ has joined #openstack-searchlight | 09:17 | |
| *** TravT has quit IRC | 09:25 | |
| *** yingjun_ has quit IRC | 09:32 | |
| *** ig0r_ has quit IRC | 09:41 | |
| *** TravT has joined #openstack-searchlight | 10:22 | |
| *** TravT has quit IRC | 10:31 | |
| *** TravT has joined #openstack-searchlight | 10:36 | |
| *** TravT has quit IRC | 10:51 | |
| *** GB21 has joined #openstack-searchlight | 11:05 | |
| *** GB21 has quit IRC | 11:15 | |
| *** TravT has joined #openstack-searchlight | 11:51 | |
| *** TravT has quit IRC | 12:00 | |
| *** TravT has joined #openstack-searchlight | 12:06 | |
| *** TravT has quit IRC | 12:14 | |
| *** TravT has joined #openstack-searchlight | 12:15 | |
| *** TravT has quit IRC | 12:20 | |
| *** TravT has joined #openstack-searchlight | 12:25 | |
| *** yingjun_ has joined #openstack-searchlight | 12:25 | |
| *** yingjun_ has quit IRC | 12:30 | |
| *** TravT has quit IRC | 12:34 | |
| *** yingjun_ has joined #openstack-searchlight | 12:35 | |
| *** TravT has joined #openstack-searchlight | 12:39 | |
| *** yingjun_ has quit IRC | 12:42 | |
| *** yingjun_ has joined #openstack-searchlight | 12:42 | |
| *** TravT has quit IRC | 12:43 | |
| *** yingjun_ has quit IRC | 12:47 | |
| *** TravT has joined #openstack-searchlight | 13:07 | |
| *** TravT has quit IRC | 13:17 | |
| *** TravT has joined #openstack-searchlight | 13:17 | |
| openstackgerrit | Harshada Mangesh Kakad proposed openstack/searchlight: Replace deprecated library function os.popen() with subprocess https://review.openstack.org/267555 | 13:24 |
| *** TravT has quit IRC | 13:30 | |
| *** TravT has joined #openstack-searchlight | 13:36 | |
| *** yingjun_ has joined #openstack-searchlight | 13:40 | |
| *** TravT has quit IRC | 13:45 | |
| *** TravT has joined #openstack-searchlight | 13:46 | |
| *** TravT has quit IRC | 13:55 | |
| *** TravT has joined #openstack-searchlight | 14:00 | |
| *** TravT has quit IRC | 14:18 | |
| *** TravT has joined #openstack-searchlight | 14:19 | |
| *** TravT has quit IRC | 14:24 | |
| *** TravT has joined #openstack-searchlight | 14:29 | |
| *** yingjun has quit IRC | 14:33 | |
| *** TravT has quit IRC | 14:38 | |
| *** GB21 has joined #openstack-searchlight | 14:46 | |
| *** yingjun_ has quit IRC | 14:54 | |
| *** yingjun has joined #openstack-searchlight | 14:54 | |
| *** TravT has joined #openstack-searchlight | 15:00 | |
| TravT | Courtesy Searchlight meeting reminder now in #openstack-meeting-4: lakshmiS, nikhil_k, rosmaita, sigmavirus24, TravT, david-lyle, kragniz, sjmc7, ekarlso, abhijeetm, itisha, GB21, briancline, lei-zh-, yingjun | 15:00 |
| *** TravT has quit IRC | 15:01 | |
| *** TravT has joined #openstack-searchlight | 15:02 | |
| *** sigmavirus24_awa is now known as sigmavirus24 | 15:07 | |
| *** TravT has quit IRC | 15:20 | |
| *** TravT has joined #openstack-searchlight | 15:21 | |
| *** RickA-HP has joined #openstack-searchlight | 15:59 | |
| TravT | yingjun: what are your thoughts on everything we just discussed in the meeting? | 16:00 |
| *** GB21 has quit IRC | 16:00 | |
| TravT | i guess i'll summarize current options again. | 16:01 |
| yingjun | i’d prefer openstack search query | 16:01 |
| yingjun | and adding optional arguments if needed | 16:02 |
| TravT | so then | 16:02 |
| TravT | https://review.openstack.org/#/c/260899 | 16:02 |
| TravT | really just chances the command from resources to query | 16:03 |
| TravT | openstack search query [—type [<resource-type> [<resource-type>…]]] [--query-string <query-string>] [--all-projects] [--details] | 16:03 |
| TravT | and we add follow patch with --native for a full native query | 16:04 |
| TravT | openstack search query [—type [<resource-type> [<resource-type>…]]] [--query-string <query-string>] [--native <json>] [--all-projects] [--details] | 16:04 |
| sjmc7 | what does it mean if you don’t provide --query-string? | 16:05 |
| TravT | and possibly a --simple-query-string | 16:05 |
| yingjun | defaults to match everything | 16:05 |
| RickA-HP | And the user can specify only one of the options [ --query-string | --native | --simple-query-string ] | 16:06 |
| TravT | hmm, [ [--query-string <query-string>] | [--native <json>] | [--simple-query-string] ] | 16:06 |
| rosmaita | TravT: sorry i missed the mtg | 16:06 |
| TravT | rosmaita: yeah, we missed you! | 16:07 |
| TravT | still time to catch up! | 16:07 |
| TravT | i think perhaps more interesting than usual today | 16:07 |
| TravT | http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-01-14-15.01.log.html | 16:07 |
| TravT | FYI | 16:07 |
| TravT | so yingjun, RickA-HP, sjmc7, if it is just a [ --query-string | --native | --simple-query-string ] | 16:08 |
| TravT | then will it become really complex figuring out what additional parameter options are possible with each one? | 16:09 |
| TravT | going back to some of sjmc7s questions about sorting, etc. | 16:09 |
| sjmc7 | if you think there’d be different options then yes, it will become very complex | 16:09 |
| RickA-HP | The --native option is easy! | 16:10 |
| TravT | that's why perhaps the | 16:11 |
| RickA-HP | Going back to Steve's question about a default, I agree with yingjun in that it would match everything. If no option is specified it would default to "--native '{ "query" : { "math_all" : {} } }' | 16:11 |
| sjmc7 | i’m not really a big fan of mandatory optional arguments | 16:11 |
| TravT | with some limit... | 16:11 |
| TravT | sjmc7: please expand? | 16:12 |
| openstackgerrit | Li Yingjun proposed openstack/python-searchlightclient: Add facet list support https://review.openstack.org/255027 | 16:12 |
| sjmc7 | with a default i think it’s better | 16:13 |
| sjmc7 | i’d still prefer to make it smart if we can | 16:13 |
| sjmc7 | detecting whether you’re trying a query string versus a json payload isn’t hard | 16:13 |
| TravT | ok, couple examples again? :) | 16:14 |
| sjmc7 | search query “name: something” | 16:14 |
| sjmc7 | search query ‘{“term”: {“field”: “name”, “query”: “something”}}' | 16:14 |
| TravT | that is nice. | 16:15 |
| sjmc7 | that’s a bit harder if you want to support | 16:15 |
| sjmc7 | search query ‘“match_all”: {}' | 16:15 |
| sjmc7 | though even then, if the CLI can parse it as JSON with surrounding brackets | 16:15 |
| sjmc7 | then it probably is | 16:16 |
| TravT | and for simple string query support | 16:16 |
| TravT | how do we figure it out? | 16:16 |
| sjmc7 | you could also use —query-stirng as a flag | 16:16 |
| sjmc7 | what’s ‘simple query string’? i think i missed that | 16:16 |
| ekarlso | anything I can help with ? :p | 16:17 |
| TravT | simple-query-string --> https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-simple-query-string-query.html | 16:17 |
| sjmc7 | ekarlso - there’re a bunch of reviews need doing, and a few bugs | 16:17 |
| TravT | ekarlso, we're having debates on CLI | 16:17 |
| sjmc7 | goodness gracious | 16:17 |
| sjmc7 | that doesn’t seem simple :) | 16:18 |
| TravT | definitely if you want to reach the meeting logs from today and catch up | 16:18 |
| TravT | http://eavesdrop.openstack.org/meetings/openstack_search/2016/openstack_search.2016-01-14-15.01.log.html | 16:18 |
| sjmc7 | i’d use a flag | 16:18 |
| TravT | --syntax | 16:18 |
| sjmc7 | openstack search query “magical simple string” —simple-query-string | 16:18 |
| sjmc7 | i prefer the structure of a mandatory positional argument, and optional flags to alter behavior | 16:18 |
| sjmc7 | the default would then be equivalent to —native | 16:19 |
| sjmc7 | and if possible make the CLI try to figure it out | 16:19 |
| TravT | that seems pretty reasonable... | 16:19 |
| rosmaita | just want to interject that the complexity of this issue has exceeded my available brain cells ATM, so i'm not going to express an opinion | 16:19 |
| TravT | i still would like the faceted query idea though | 16:19 |
| sjmc7 | mine too rosmaita :) | 16:20 |
| sjmc7 | honestly, i’d like to get the simpelst useful thing merged | 16:20 |
| TravT | rosmaita: LOL | 16:20 |
| sjmc7 | and then go from there | 16:20 |
| rosmaita | bummer, because i was going to say, i will go with what sjmc7 says! | 16:20 |
| sjmc7 | lesson learned! | 16:20 |
| RickA-HP | Do we think that the "--native" vs "query-string" vs "simple-query-string" are different enough that we can easily detect which is which in the CLI? | 16:20 |
| sjmc7 | simple vs query-string, no | 16:21 |
| RickA-HP | I would hate for the CLI being too smart and returning the wrong query that the user is not expecting! | 16:21 |
| TravT | i think --query-type | 16:21 |
| sjmc7 | however, i’ve never used simple query string | 16:21 |
| TravT | sjmc7 i played with it as part of the ui dev | 16:21 |
| sjmc7 | the docs make it sound like a query_string that silently eats errors | 16:22 |
| TravT | it was a little more forgiving | 16:22 |
| TravT | but if i remember right, not quite as powerful | 16:22 |
| sjmc7 | RickA-HP: i think reliably we can determine query vs query-string | 16:23 |
| TravT | in either case, they all have these extra params | 16:23 |
| TravT | that differ based on query type | 16:23 |
| RickA-HP | Would we pass in the simple-query-string as is? For example will we allow the user to specify an analyzer? | 16:23 |
| sjmc7 | i’m struggling to understand why we’d try to provide options for all this | 16:24 |
| sjmc7 | if you’re doing a really crazy query, do it with json | 16:24 |
| sjmc7 | otherwise we’re trying to reinterpret the DSL | 16:24 |
| TravT | so, i generally like simplest approach | 16:25 |
| RickA-HP | Steve, are you proposing not to have simple-query-string and to limit what we allow for query-string? | 16:25 |
| TravT | but i don't like backing into a corner | 16:25 |
| TravT | and on the UI, definitely found some of the extra params very nice | 16:25 |
| TravT | like phrase slop | 16:25 |
| sjmc7 | the UI isn’t USING the cli | 16:25 |
| sjmc7 | here’s the problem | 16:26 |
| sjmc7 | if we have, say 100 options | 16:26 |
| TravT | the UI defnitely isnt' using the CLI | 16:26 |
| sjmc7 | we have to document all of them, and make sure we target a specific e-s API version | 16:26 |
| TravT | but it is really nice to put in a simple query without a bunch of json and be able to say "please don't use exact phrase matching" --> eg phrase_slop != 0 | 16:27 |
| TravT | i'm thinking we could do | 16:27 |
| TravT | basically what you are saying | 16:27 |
| TravT | but have ability to pass through additional query type params. | 16:28 |
| RickA-HP | Travis, I think your Wifi is dropping again! | 16:28 |
| TravT | hmm | 16:28 |
| TravT | why? | 16:28 |
| sjmc7 | ok. what are you wanting yingjun to do for these patches? | 16:29 |
| sjmc7 | my vote is still to support openstack search query <json blob> | 16:29 |
| sjmc7 | and go from there | 16:29 |
| TravT | as mentioned at end of the meeting | 16:29 |
| RickA-HP | Steve, do you mean the first patch would do 'JSON blob' only? | 16:29 |
| sjmc7 | yes. | 16:29 |
| TravT | 08:58 TravT: it seems that this patch is ready except for some confusion i have on making it work with devstack | 16:30 |
| TravT | 08:58 TravT: https://review.openstack.org/#/c/249076 | 16:30 |
| TravT | 08:58 TravT: and this patch https://review.openstack.org/#/c/255027/ | 16:30 |
| TravT | 08:59 TravT: just needs --resource changed to --type | 16:30 |
| sjmc7 | ok, good | 16:30 |
| TravT | yingjun already fixed the above | 16:30 |
| TravT | 255027 | 16:30 |
| TravT | the last one https://review.openstack.org/#/c/260899/ | 16:30 |
| TravT | sounds like we are leaning towards a sytnax like this | 16:31 |
| TravT | openstack search query <json or string which client figures out> [—type [<resource-type> [<resource-type>…]]] [--all-projects] [--details] | 16:32 |
| yingjun | ok | 16:32 |
| sjmc7 | ok, i’m good with that | 16:33 |
| TravT | with possibility of sending additional params through | 16:33 |
| TravT | e.g. phrase_slop.... | 16:33 |
| RickA-HP | We will need to define what "string" supports. Starting with a few options as needed. | 16:33 |
| TravT | i'm kind of thinking that we could treat any unrecognized param e.g. --phrase_slop as something that we just pass straight through. | 16:34 |
| RickA-HP | If this is too large, we can go with Steve's idea of support JSON blob only for the first patch and then follow it up with the simple search string in a subsequent patch. | 16:34 |
| TravT | to be clear, yingjun's patch already support query string, i thinkg | 16:34 |
| TravT | not json blob | 16:34 |
| sjmc7 | that’s fine too, either works as a start point | 16:35 |
| TravT | line 41 here: https://review.openstack.org/#/c/260899/1/searchlightclient/osc/v1/search.py | 16:35 |
| RickA-HP | Ok | 16:35 |
| TravT | and line 78 | 16:35 |
| TravT | well, then i think we're in agreement. ? | 16:36 |
| yingjun | sorry guys, i have to take care of my crying baby, please comment in the patch if any conclusion come out.. and i’ll do the change. | 16:36 |
| ekarlso | so baically a discussion on how to implement query stuff from a cli perspective ? | 16:37 |
| TravT | yingjun: no, our apolozies to you! | 16:37 |
| ekarlso | yingjun: heh, I know that problem ;) | 16:37 |
| TravT | ekarlso: yeah | 16:37 |
| RickA-HP | Travis, I believe we are in agreement. | 16:37 |
| TravT | ok, i'll add comment on patch | 16:37 |
| TravT | openstack search query <json or string which client figures out> [—type [<resource-type> [<resource-type>…]]] [--all-projects] [--details] | 16:37 |
| TravT | thanks for pounding through this. | 16:39 |
| TravT | just didn't want to see these patches quagmired for ever. :) | 16:39 |
| RickA-HP | Just in time, the way the wind is blowing off the mountains I may be joining you in Wifi limbo. | 16:39 |
| TravT | yeah, it's crazy! | 16:39 |
| TravT | i keep expecting a tree to come flying through the window | 16:40 |
| ekarlso | lol, you should've seen the weather here in december :P | 16:41 |
| ekarlso | record rains and winds : P | 16:41 |
| RickA-HP | Where is that, in the South? | 16:43 |
| ekarlso | RickA-HP: Norway :P | 16:43 |
| RickA-HP | ekarlso Yikes, stay dry! | 16:43 |
| *** yingjun has quit IRC | 16:46 | |
| *** yingjun has joined #openstack-searchlight | 16:54 | |
| *** nikhil_k has joined #openstack-searchlight | 17:27 | |
| *** nikhil has quit IRC | 17:29 | |
| sjmc7 | i’d really like to get https://review.openstack.org/#/c/266587/ merged; it makes it a lot easier to add tests for other plugins we work on | 17:29 |
| krotscheck | TravT: In response to https://review.openstack.org/#/c/265396/ - I can just remove the http methods. | 17:33 |
| krotscheck | TL/DR my comment: If we miss something, there's easy workarounds available | 17:34 |
| openstackgerrit | Michael Krotscheck proposed openstack/searchlight: Added Keystone and RequestID headers to CORS middleware https://review.openstack.org/265396 | 17:35 |
| sjmc7 | TravT / lakshmiS / RickA-HP - any thoughts on https://bugs.launchpad.net/searchlight/+bug/1532972 | 17:39 |
| openstack | Launchpad bug 1532972 in OpenStack Search (Searchlight) "Restructure parent-child plugins" [Medium,New] | 17:39 |
| sjmc7 | i think neutron’s going to be parent/child and suffer from the same problem | 17:40 |
| *** GB21 has joined #openstack-searchlight | 17:59 | |
| *** nikhil_k is now known as nikhil | 18:11 | |
| TravT | sjmc7 i do agree it is problematic and i recall us pondering that at the time. are you just thinking of combining to single plugin | 18:11 |
| TravT | but still have the two types? | 18:12 |
| sjmc7 | i think keep the separate plugins, but make the relationship known at index time | 18:12 |
| sjmc7 | so either zone knows ‘recordset’ is a child or the other way round | 18:12 |
| sjmc7 | and don’t index ‘children’ independently | 18:12 |
| sjmc7 | everything else, i think, can remain the same | 18:13 |
| TravT | is there value to keeping separate plugin? | 18:14 |
| sjmc7 | being able to search them independently | 18:14 |
| *** sigmavirus24 is now known as sigmavirus24_awa | 18:15 | |
| TravT | ok, i'm confused | 18:15 |
| TravT | reading the bug it says: It doesn't make sense for Zone to be a first-class plugin. | 18:16 |
| sjmc7 | it doesn’t make sense to INDEX it as a first class plugin | 18:16 |
| sjmc7 | yes, i wasn’t very clear | 18:17 |
| sjmc7 | there’s no problem searching RecordSet separately | 18:17 |
| sjmc7 | it doesn’t make sense to *index* RecordSet | 18:17 |
| TravT | okay, now that seems a little more clear, especially since zone is the parent | 18:18 |
| sjmc7 | i’ll edit the description, it’s not very clear | 18:19 |
| sjmc7 | in my brain it made sense | 18:19 |
| *** sigmavirus24_awa is now known as sigmavirus24 | 18:19 | |
| TravT | no worries. i often find that by the time my thoughts reach my fingers that they must taken a detour along the way. | 18:19 |
| sjmc7 | yeah, i should’ve written ‘RecordSet’ too :) | 18:20 |
| sjmc7 | yeah, i think i’m right; reindexing RecordSets makes no sense on their own | 18:21 |
| TravT | no, not really | 18:21 |
| sjmc7 | since you have to also ensure Zones exist | 18:22 |
| sjmc7 | so i think it’s fine to allow searches to treat them separately | 18:22 |
| sjmc7 | but for indexing i think we’d present it as | 18:22 |
| sjmc7 | - OS::Nova::Server | 18:22 |
| sjmc7 | - OS::Designate::Zone (OS::Designate::Recordset) | 18:22 |
| TravT | That could work | 18:24 |
| TravT | other than maybe something to do with performance i'm not sure of a value to not doing it that way | 18:25 |
| sjmc7 | right now i think it’s broken | 18:31 |
| sjmc7 | with the notifications we can somewhat rely on a zone existing before we try to index recordsets for it, but if you’re reindexing that’s not necessarily the case | 18:32 |
| *** bpokorny has joined #openstack-searchlight | 18:32 | |
| TravT | well, that's interesting. | 18:38 |
| TravT | because recordset notifications happen independent of zone notificatoins | 18:38 |
| sjmc7 | right, so that’s fine | 18:38 |
| sjmc7 | because if we presume we’re up to date with zones we should be ok updating recordsets | 18:39 |
| TravT | just read your updated description | 18:40 |
| sjmc7 | i’m bringing this up because it will affect neutron, presuming we treat subnets and ports as children of networks | 18:41 |
| sjmc7 | simplest option, of course, is to not do parent-child at all | 18:41 |
| TravT | i can say that at a concept level, what you are saying seems right, but i'm not visualizing the concrete code change being suggested yet | 18:41 |
| sjmc7 | initial_indexing won’t do anything for recordsets - recordsets will mark itself as a child of ‘zones' | 18:42 |
| sjmc7 | and the mapping and indexing will be driven from there | 18:42 |
| TravT | very small lightbulb finally started light up | 18:42 |
| TravT | that makes sense i believe. | 18:43 |
| TravT | humor me and let me restate in my own words. | 18:43 |
| TravT | searchlight-manage index sync will not let you specify OS::Designate::Recordset on its own and if you don't specify anything it just lists OS::Designate::Zone (OS::Designate::Recordset) | 18:44 |
| sjmc7 | i think for the sake of efficiency, it’s ok to index all Zones, and then all Recordsets | 18:44 |
| sjmc7 | right | 18:44 |
| sjmc7 | yeah - relaly, that’s the only difference | 18:44 |
| TravT | yeah, some algorithm would be fine | 18:45 |
| sjmc7 | the issue is, for something like neutron, it makes reindexing quite expensive | 18:45 |
| TravT | not sure if there'd be a race condition, but that must already exist | 18:45 |
| sjmc7 | although since there are at least as many children as parents, maybe that’s ok | 18:45 |
| sjmc7 | reindexing Networks independently of Ports would make no sense | 18:46 |
| TravT | it is kind of weird to conceptually think about "let me reindex all my records because i now my zones are all correct" | 18:46 |
| TravT | now -> know | 18:46 |
| TravT | agree it could get expensive, but you'd have to be pretty brilliant to realize that only one type of child entity is out of whack | 18:47 |
| TravT | it is likely more error prone to not index from parent on down. | 18:48 |
| *** bpokorny_ has joined #openstack-searchlight | 18:49 | |
| sjmc7 | grr, having wifi issues of my own | 18:50 |
| *** bpokorny_ has quit IRC | 18:50 | |
| sjmc7 | i missed anything since 12:47 | 18:50 |
| *** bpokorny_ has joined #openstack-searchlight | 18:51 | |
| *** bpokorny has quit IRC | 18:53 | |
| TravT | just me writing a note on the notification forwarding spec | 18:54 |
| *** bpokorny_ has quit IRC | 18:55 | |
| *** bpokorny has joined #openstack-searchlight | 18:56 | |
| sjmc7 | you want me to +2 it? | 18:58 |
| sjmc7 | i will do so, but i’m not intending to spend any time implementing it | 18:59 |
| *** bpokorny has quit IRC | 19:01 | |
| TravT | let's wait to see what reply happens from what i posted | 19:10 |
| *** RickA-HP has quit IRC | 19:15 | |
| openstackgerrit | Travis Tripp proposed openstack/searchlight: Add python 3.4 to programming languages in setup.cfg https://review.openstack.org/267783 | 19:20 |
| *** lakshmiS has joined #openstack-searchlight | 19:32 | |
| *** TravT_ has joined #openstack-searchlight | 19:44 | |
| *** TravT has quit IRC | 19:48 | |
| *** TravT_ has quit IRC | 19:51 | |
| *** TravT has joined #openstack-searchlight | 19:52 | |
| *** yingjun has quit IRC | 19:53 | |
| *** yingjun has joined #openstack-searchlight | 19:53 | |
| *** yingjun has quit IRC | 19:57 | |
| *** TravT has quit IRC | 19:58 | |
| *** TravT has joined #openstack-searchlight | 20:03 | |
| *** TravT has quit IRC | 20:23 | |
| *** TravT has joined #openstack-searchlight | 20:24 | |
| *** GB21 has quit IRC | 20:28 | |
| *** TravT has quit IRC | 20:31 | |
| *** TravT has joined #openstack-searchlight | 20:32 | |
| *** TravT_ has joined #openstack-searchlight | 20:43 | |
| *** TravT has quit IRC | 20:44 | |
| *** TravT has joined #openstack-searchlight | 20:50 | |
| *** TravT_ has quit IRC | 20:50 | |
| *** TravT_ has joined #openstack-searchlight | 20:55 | |
| *** TravT has quit IRC | 20:55 | |
| *** bpokorny has joined #openstack-searchlight | 21:05 | |
| *** TravT_ has quit IRC | 21:06 | |
| *** TravT has joined #openstack-searchlight | 21:07 | |
| *** TravT_ has joined #openstack-searchlight | 21:13 | |
| *** TravT has quit IRC | 21:13 | |
| *** TravT_ has quit IRC | 21:21 | |
| *** TravT has joined #openstack-searchlight | 21:21 | |
| *** TravT has quit IRC | 21:28 | |
| *** TravT has joined #openstack-searchlight | 21:28 | |
| *** TravT has quit IRC | 21:36 | |
| *** TravT has joined #openstack-searchlight | 21:37 | |
| *** TravT_ has joined #openstack-searchlight | 21:43 | |
| *** TravT has quit IRC | 21:43 | |
| *** TravT has joined #openstack-searchlight | 21:50 | |
| *** TravT_ has quit IRC | 21:50 | |
| *** TravT_ has joined #openstack-searchlight | 21:53 | |
| *** TravT has quit IRC | 21:54 | |
| *** TravT has joined #openstack-searchlight | 22:10 | |
| *** TravT_ has quit IRC | 22:12 | |
| *** TravT_ has joined #openstack-searchlight | 22:15 | |
| *** TravT has quit IRC | 22:16 | |
| *** TravT has joined #openstack-searchlight | 22:21 | |
| *** TravT_ has quit IRC | 22:23 | |
| *** TravT_ has joined #openstack-searchlight | 22:26 | |
| *** TravT has quit IRC | 22:28 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 22:59 | |
| TravT_ | sjmc7: u there? | 23:02 |
| *** TravT_ is now known as TravT | 23:02 | |
| *** bpokorny_ has joined #openstack-searchlight | 23:17 | |
| *** bpokorny has quit IRC | 23:20 | |
| openstackgerrit | Steve McLellan proposed openstack/searchlight: WIP Index child plugins as part of parent https://review.openstack.org/267864 | 23:47 |
| *** TravT has quit IRC | 23:54 | |
| *** TravT has joined #openstack-searchlight | 23:55 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!