| * ndushay joins | 01:44 | |
| * _mst leaves | 03:18 | |
| * _mst joins | 03:20 | |
| * ndushay leaves | 03:59 | |
| * cbeer_ leaves | 08:17 | |
| * cbeer_ joins | 08:37 | |
| * bess joins | 09:10 | |
| * bess leaves | 09:13 | |
| * bess joins | 09:31 | |
| * bess leaves | 09:40 | |
| * bess joins | 09:41 | |
| * bess leaves | ||
| * bess joins | 09:48 | |
| * erikhatcher leaves | 09:49 | |
| * erikhatcher joins | 09:57 | |
| * bess leaves | 10:07 | |
| * erikhatcher leaves | 10:16 | |
| * jamieorc joins | 10:30 | |
| * mmitchell joins | 10:56 | |
| <jrochkind> | mmitchell: hey, you wanna talk about rake solrmarc for a minute? | 11:13 |
| <mmitchell> | jrochkind: sure | |
| <jrochkind> | mmitchell: so, if you wanna see what the current one does, if you run rake solr:marc:index:info, it gives you some good clues. | |
| <mmitchell> | jrochkind: right, now i do remember seeing that. | 11:14 |
| <jrochkind> | mmitchell: however, the SolrMarc 2.1 version, which I'll have in a public branch today hopefully, simplifies things somewhat, cause SM 2.1 provides some things that allow more simplicity. | |
| mmitchell: But basically, what's it's gonna do: It first looks for $RAILS_ROOT/vendor/plugins/blacklight/config/SolrMarc/config(-RAILS_ENV).properties. | ||
| <mmitchell> | jrochkind: excellent. i've been meaning to get over and talk to Bob about some of the changes. | |
| jrochkind: ok | 11:15 | |
| <jrochkind> | mmitchell: If it doesn't find it there, it looks in $RAILS_ROOT/config/SolrMarc.... . | |
| This latter one could find it in two cases: 1) You actually do have a custom rails app with the plugin installed, but have your own local config/SolrMarc. 2) You are running the rake task _from_ the plugin as if it were a rails app, as developers tend to do. | ||
| <mmitchell> | jrochkind: right makes sense | |
| jrochkind: so we're actually not too far off then | 11:16 | |
| <jrochkind> | (I actually took the config-RAILS_ENV.properties OUT of the SM 2.1 branch, cause nobody was using it, but I'll put it back in. | |
| mmitchell: So for the moment, I'll finish off what I was gonna do and put it in a public branch. Then I'll let you figure out how to use it for the test solr architecture you want. But I think you can probably re-use a lot of the code. | ||
| mmitchell: Also, ALL the various properties (where the config.properties is, etc) can be explicitly set by ENV variables. It just looks for those others as defaults if you don't do that. | 11:17 | |
| <mmitchell> | jrochkind: that sounds great. looking forward to seeing it | |
| jrochkind: nice :) | ||
| <jrochkind> | mmitchell: So, you can probably just use the existing rake task but set the location of the marc file and such, and boom, you have your test indexer. | |
| mmitchell: one question/issue I'd like to share. Right now it does not use solrconfig.yml, the ports are just set in config.properties, as is standard for solrmarc. But... | 11:18 | |
| mmitchell: I looked into making the rake task load the whole Rails environment, so you could set whatever defaults you wanted in your standard environments/development.rb etc. But that made the rake task take like 3 or 4 seconds more to start. boo. | ||
| <mmitchell> | jrochkind: hmm, so you're saying, use the solr.yml files for some settings (port etc.)? | 11:19 |
| <jrochkind> | So then I considered having the rake task load a single config/SolrMarc/environment.rb, where you could put that stuff. But I'm not sure about that. There are other possibilities, like having it load the solrconfig.yml itself (not use the Rails environment) but load it itself. | |
| <mmitchell> | jrochkind: that SM would use? | |
| <jrochkind> | Well, right now it doesn't use solr.yml at all. It just expects all that stuff will be in config.properties, cause that's what all the SolrMarc stock examples do. | 11:20 |
| But it potentially COULD. There are a buncha possiblities. Not sure what is best. So I guess I'll leave it to you, to figure out what we need for this actual use case, instead of just trying to design for all possibilities. But I'm happy to help code if you figure out what's needed, heh. | ||
| So, one flaw in putting solr.path in the config.properties file as it's done now. That path you saw that you thought was crazy WAS the right path for when you have BL installed as a plugin, and a jetty up next to your app. That is, it was the right path IF the config.properties is in the plugin! | 11:21 | |
| But let's say you want to localize the config.properties. So you copy it into your local app. The first thing you're going to need to do is change that relative path, cause it ain't right anymore. | ||
| <mmitchell> | jrochkind: great yeah, i see how that could be useful. keeping things DRY etc. I kinda like the idea of keeping everything related to a solr connection in solr.yml. And then anything that's specifically for SM, in the properties file. but maybe we can get some feedback from the community too. | |
| jrochkind: yeah, so if everything is done via rake, then you wouldn't have to do that right? | 11:22 | |
| <jrochkind> | Yeah, IF we put the stuff we want like that in rake. | |
| mmitchell: I agree, it does have a DRY charm. But I'm not sure how much time I want to spend on making it do crazy stuff, cause ultimately I suspect replacing SolrMarc as an independent tool with erikhatcher's solr update handler approach. | ||
| And that approach the rake task will ONLY need the solr host/port, which is already in solrconfig.yml. So I'm not sure how much complicated infrastructure to put in place for SolrMarc as it is now. | 11:23 | |
| <mmitchell> | jrochkind: so, let's just stick with the easiest/simplest approach for now, and see how it feels | |
| <jrochkind> | mmitchell: Exactly. I'll have my public branch that has a solr:marc:index that works pretty much the way it always did, but with SM 2.1. You can look at it and see what you want to do. | 11:24 |
| Keep in mind that 'pretty much how it always did' requires the solr.path staying the same, heh. | ||
| But it would be easy to have a config-test.properties and a config.properties, or whatever. There are a buncha possibilities. | 11:25 | |
| <mmitchell> | jrochkind: awesome | |
| <jrochkind> | okay, cool, thanks. | |
| <mmitchell> | jrochkind: thank you! good stuff. | |
| <jrochkind> | yeah, I was already working on this anyway, cause I wanted to take advantage of the SM 2.1 features, and I liked the convenience of the solr:marc:index rake task (which I may be the only one presently using, heh). | |
| * bess joins | 11:28 | |
| * bess leaves | ||
| * ndushay joins | 11:33 | |
| * ndushay leaves | 12:39 | |
| * ndushay joins | 13:07 | |
| * mmitchell leaves | 13:23 | |
| * ndushay leaves | 13:53 | |
| * ndushay joins | 13:59 | |
| * erikhatcher joins | 14:06 | |
| * bess joins | 14:10 | |
| * ndushay leaves | 14:48 | |
| * ndushay joins | 14:59 | |
| * erikhatcher leaves | 15:26 | |
| * jamieorc leaves | 15:32 | |
| * bess leaves | 15:50 | |
| * erikhatcher joins | 16:18 | |
| * erikhatcher leaves | 16:26 | |
| * erikhatcher joins | 16:59 | |
| * erikhatcher leaves | 17:13 | |
| * erikhatcher joins | 17:21 | |
| * erikhatcher leaves | 17:32 | |
| * erikhatcher joins | 17:39 | |
| * erikhatcher leaves | 17:42 | |
| * jrochkind leaves | 18:08 | |
| * cbeer_ leaves | ||
| * BillDueber leaves | ||
| * BillDueber joins | 18:09 | |
| * jrochkind joins | 18:10 | |
| * bess joins | 18:32 | |
| * bess leaves | 18:48 | |
| * Naomi joins | 19:23 | |
| * ndushay leaves | 19:25 | |
| * cbeer_ joins | 19:31 | |
| * ndushay leaves | 20:08 | |
| * erikhatcher joins | 20:12 | |
| * erikhatcher leaves | 22:21 | |
| * wlayton joins | 23:19 | |
| * wlayton leaves | 00:13 | |
Generated by Sualtam