Searchable plugin – Lucene search on numeric values

Aman Aggarwal — Wed, 14 Jul 2010 18:15:47 +0000

While using searchable plugin for the first time, I wasn’t aware that lucene implements only lexicographic comparisons for searching on indexed values (even on numeric fields). Before I learned this, I kept on wondering why a Person of age 6 always appeared in search results when I look for People more than 20 years of age. The solution was to define a transient field ageIndexValue in domain class Person and implement its getter as:

String getAgeIndexValue() {
    return org.apache.lucene.document.NumberTools.NumberTools.longToString(this.age)
}

Also, you will need to change the search query from

q=age:[20 TO *] to q=ageIndexValue:[0000000000000u TO *]

where, 0000000000000u == org.apache.lucene.document.NumberTools.longToString(20L)

~Aman Aggarwal
aman@intelligrape.com

http://www.IntelliGrape.com/

Configuring multiple senders in Grails Mail plugin

Abhishek Tejpaul — Mon, 14 Jun 2010 06:21:58 +0000

In one of the recent projects, we had to set up a system where emails for different purposes (i.e registration, error reporting etc.) were to be sent out from different email accounts. We were using the Grails Mail plugin which does not provide a clear way to set-up or configure multiple email addresses. With the help of my colleague, Chandan Luthra, I tried to dig into the workings of plugin and found out that Mail plugin injects the properties such as username, password etc. through a bean named mailSender. So we just did the following to customize/configure these properties on the fly from the controller or a service:

CH.config.grails.mail.default.from = "username@domain.com" // Mail plugin uses this to connect to the account in e-mail provider's server. So it should be set.
mailSender.username = "username@domain.com"
mailSender.password = "sample123!"

And yes, once you are done with your email sending functionality you can set mailSender properties back to the default settings set originally in Config.groovy. Your service/controller code could look something like this:

// Store the default mail settings in variables
def defaultFrom = CH.config.grails.mail.default.from
String oldUsername = mailSender.username
String oldPassword = mailSender.password

// Change the properties here; send the email
try {
CH.config.grails.mail.default.from = "username@domain.com"
mailSender.username = "username@domain.com"
mailSender.password = "sample123!"
mailService.sendMail {
to(['exampple1@domain1.com', 'example2@domain2.com'].toArray())
subject("Example Subject")
body("Sample body")
}
}
catch (Exception e) {
// catch block code
}
// Set the original settings back
finally {
CH.config.grails.mail.default.from = defaultFrom
mailSender.username = oldUsername
mailSender.password = oldPassword
}

I guess this scenario can be quite prevalent in many projects. Hope you find the blog useful.

- Abhishek Tejpaul

Intelligrape Software Pvt. Ltd.

[www.intelligrape.com]

Intelligrape Groovy & Grails Blogs » plugin

Searchable plugin – Lucene search on numeric values

Configuring multiple senders in Grails Mail plugin