> Good question! It looks like it just prints the metadata in any order, as > opposed to the order that you received it. This is probably not a great thing > to do, so > can you file an issue and we can take a look at it?
Great! I'll file an issue and start debugging it to find a solution unless you bestme to it. I'm glad that it is an issue and not just bad query syntax. > http://oodt.apache.org/components/maven/apidocs/org/apache/oodt/cas/filemgr/util/SqlParser.html Thanks. I'll take a look. > Improvements welcome! :) Cool. > >> • The Lucene query returns the productID. Is there a class I can use that >> will return something similar to the sql query? (Although I should look at >> the code and find this out for myself - asking is free :-) > > Heh, great question, but the answer is no. We didn't really standardize on > the output from these tools. I originally developed the QueryTool (which > understood Lucene to begin with, and later Brian Foster added his SQL syntax > to it, and the associated response format). > > Maybe we should open up an issue (and associated wiki page) on standardizing > on the output. Feel free to propose something and I'll be happy to join in > (hopefully others will too). Thanks. I'm really amped to get my hands dirty with Lucene. I'll see what I can come up with once I've spend some time on Lucene. > >> • I've not yet tested any more complex SQL and Lucene queries - I was >> just wondering if there where any useful info out there that would show me >> some more funky example queries. So far I've found lucene tutorial and sql >> quick ref. I'll tie this into OODT Filemgr User Guide once I've figured >> these things out. > > +1, that's the best place to start. We also only support a limited set of the > Lucene syntax as well, see the following class: > > http://oodt.apache.org/components/maven/apidocs/org/apache/oodt/cas/filemgr/tools/CASAnalyzer.html Thanks. > >> • I see the version of lucene being used it quiet old (2.0.0 and the >> latest ver is 2.9.1). Is there any reason why OODT is using this old version? > > I would *love* to upgrade to 2.9.1 or 2.9.4. > > Upgrading to 3.0 will break APIs for us, b/c Lucene changed to the > ScoreCollector method for getting hits back I believe in the 3.x > series, however we should be forwards compat to e.g., 2.9.4. > > http://repo1.maven.org/maven2/org/apache/lucene/lucene-core/2.9.4/ Great. I'm happy to get involved in the upgrade. Perhaps the best way to learn is to give it a try and ask some questions along the way when things break. > >> • Should I be spending the effort to use a different (i.e. sql database) >> or are other OODT implementations using lucene? >> Thanks in advance for any help. > > Great question. > > Most of the folks use Lucene to begin with, because it requires no external > database or service, it just works out of the box. Okay. Once the querytool is sorted out I can take a look at these details. But it's good to know that there are migration options if I need to change. > Hope that helps explain things. Yes! Thanks! > These would probably be good javadocs, plus Wiki pages for these tools and > migration :) Sure. I'm happy to try document what i can when I get there. > Cheers, > Chris Cheers, Tom.
