I looked at the patch - do you think that something similiar will work with MySql - which is the DB we use in the Stax environment?
D. On Sat, Aug 7, 2010 at 11:46 AM, Ethan Jewett <[email protected]> wrote: > Sorry, I've been on vacation. I'm going to try to apply this in the > next day or two, but if someone else can verify that it's working and > apply the patch to trunk first, that would be great. > > Thanks, > Ethan > > On Tue, Aug 3, 2010 at 12:12 PM, Imtiaz Ahmed H E <[email protected]> wrote: >> The JDBC-only compass index case itself was not working and I have fixed >> that alone in the patch now attached to Esme Jira-205. (File >> EsmeJira205_JDBC_Only_Fix_Patch.diff) >> >> Rename the file props/compass.jdbc.cfg.xml to compass.cfg.xml & package & >> run, and you have a jdbc compass index (Derby db). >> >> The jdbc-jndi usage should be possible now with the appropriate setup of >> Compass & app container config ? >> >> Ethan, if you attend to this, let me know further... >> >> Imtiaz >> >> ----- Original Message ----- From: "Ethan Jewett" <[email protected]> >> To: <[email protected]> >> Sent: Monday, August 02, 2010 5:15 PM >> Subject: Re: Search error when using JDBC for search (was "Metadata >> handling") >> >> >> Hi Imtiaz, >> >> Using the filesystem option works fine for me if I check out the >> latest trunk and do a "mvn jetty:run". No modification to any files. >> Doing a clean checkout might be required if there is an existing >> compass index that has gotten corrupted. >> >> It should find any term that exists in a message, so just send a new >> message ("Test message" for example) and then search for a word in the >> message ("test"). If that doesn't work, then we have an issue. >> >> Ethan >> >> On Saturday, July 31, 2010, Imtiaz Ahmed H E <[email protected]> wrote: >>> >>> Ethan or anyone else, >>> >>> I have a checkout of ESME readonly without local modifications and search >>> in the non-jdbc/non-jndi case itself *appears* to be not working on my >>> system ( i.e., in the file system index case!). >>> >>> I think I'm not searching for a term that actually exists. >>> >>> So, a basic question, >>> >>> If I'm logged in and enter a term in the search box and hit return, where >>> is esme supposed to search for the term. I don't know till today. Is it >>> supposed to look for the term in *all* messages in the db regardless of >>> user/pool etc. If not, in which subset is it supposed to look? >>> >>> Imtiaz >>> >>> --- Original Message ----- From: "Anne Kathrine Petterře" >>> <[email protected]> >>> To: <[email protected]> >>> Sent: Friday, July 30, 2010 3:24 PM >>> Subject: Re: Search error when using JDBC for search (was "Metadata >>> handling") >>> >>> >>> >>> Hi, >>> >>> I am sorry but I cannot help out here either. >>> >>> Anne >>> >>> >>> On 30 July 2010 09:59, Ethan Jewett <[email protected]> wrote: >>> >>> >>> Hi Imtiaz, >>> >>> Unfortunately I do not know the answer to either of those questions >>> :-( I think we'll have to wait for Dick to give us more info on how he >>> does the Stax deployment and what worked before. >>> >>> Ethan >>> >>> On Friday, July 30, 2010, Imtiaz Ahmed H E <[email protected]> wrote: >>>> >>>> Ethan, >>>> >>>> Couple of questions: >>>> >>>> 1. I'm not familiar with the Stax environment, so I wondered if Esme > >>>> used >>> >>> Derby (JavaDB) there too for the Esme store (nothing to do with search, >>> this >>> question). >>>> >>>> 2. Re search, is it/was it ever working with just jdbc not jndi. i.e, >>> >>> with the setup of the compass config file, compass.jdbc.cfg.xml. >>>> >>>> I guess your answer will be the same as in your mail below... >>>> >>>> Imtiaz >>>> >>>> >>>> ----- Original Message ----- From: "Ethan Jewett" <[email protected]> >>>> To: <[email protected]> >>>> Sent: Thursday, July 29, 2010 5:28 PM >>>> Subject: Re: Search error when using JDBC for search (was "Metadata >>> >>> handling") >>>> >>>> >>>> >>>> Hi Imtiaz, >>>> >>>> Hopefully Dick will see this and answer at some point, because he >>>> really knows. But I do believe that it was working on Stax using the >>>> JDBC connector and then stopped working. Stax has never allowed us to >>>> use the file system, so if it was ever working on Stax then it was >>>> using the JDBC connector. >>>> >>>> Thanks, >>>> Ethan >>>> >>>> On Thu, Jul 29, 2010 at 1:39 PM, Imtiaz Ahmed H E <[email protected]> >>> >>> wrote: >>>> >>>> Ethan, >>>> >>>> Need to know - >>>> >>>> Re ESME-205, viz, Search is Broken.... >>>> >>>> Has this been implemented in the first place, with jndi/jdbc I mean...? >>> >>> And >>>> >>>> if it was, was it ever working ? >>>> >>>> Just getting into all the related stuff along with Lucene... >>>> >>>> Imtiaz >>>> >>>> ----- Original Message ----- From: "Imtiaz Ahmed H E" < >>> >>> [email protected]> >>>> >>>> To: <[email protected]> >>>> Sent: Monday, July 26, 2010 5:03 AM >>>> Subject: Re: Search error when using JDBC for search (was "Metadata >>>> handling") >>>> >>>> >>>> >>>> Will look into this and try and fix it asap. >>>> Getting to know Lucene etc...even bought the Lucene in Action book ! > >>>> The >>>> Java eco-system never ceases to give you pleasure ! >>>> >>>> Imtiaz >>>> >>>> ----- Original Message ----- From: "Ethan Jewett" <[email protected]> >>>> To: <[email protected]> >>>> Sent: Thursday, July 22, 2010 12:21 PM >>>> Subject: Re: Search error when using JDBC for search (was "Metadata >>>> handling") >>>> >>>> >>>> Not in front of my computer now, so please forgive mistakes. >>>> >>>> My testing indicated that in the Compass object in Boot.scala the >>>> conf.buildCompass() method call was failing silently during the setup >>>> of the object. >>>> >>>> The exception then occurs later on when the system attempts to use the >>>> Compass.compass value, which I believe was never populated. >>>> >>>> So, the actual failure occurs in the SearchMgr object, I think, so it >>>> has Lift methods in the stack trace, but I don't think it's a Lift >>>> issue. I'm not sure why we don't see an exception bubble up from the >>>> buildCompass() method. >>>> >>>> That is unfortunately about as far as far as I got. >>>> >>>> Ethan >>>> >>>> On Thursday, July 22, 2010, Imtiaz Ahmed H E <[email protected]> >>> >>> wrote: >>>> >>>> >>>> I mean, is this a compass thing ? but why is the exception name not >>>> printed in the log... >>>> >>>> ----- Original Message ----- From: "Imtiaz Ahmed H E" >>>> <[email protected]> >>>> To: <[email protected]> >>>> Sent: Thursday, July 22, 2010 11:39 AM >>>> Subject: Re: Search error when using JDBC for search (was "Metadata >>>> handling") >>>> >>>> >>>> >>>> So that I can take a quick step forward, can you tell me, how is the >>>> following trace produced...is this a slf4j produced log message. >>>> >>>> Andwhy is the exception name itself, I >> >> >
