Re: Solr vs Hibernate Search (Huge number of DB DMLs)
Please suggest.. On Mon, Jul 4, 2011 at 10:37 PM, fire fox fyr3...@gmail.com wrote: From my exploration so far, I understood that we can opt Solr straightaway if the index changes are kept to minimal. However, mine is absolutely the opposite. I'm still vague about the perfect solution for the scenario mentioned. Please share.. On Mon, Jul 4, 2011 at 6:28 PM, fire fox fyr3...@gmail.com wrote: Hi all, There were several places I could find a discussion on this but I failed to find the suited one for me. I'd like to be clear on my requirements, so that you may suggest me the better solution. - A project deals with tons of database tables (with *millions *of records) out of which some are to be indexed which should be searchable of-course. It uses Hibernate for MySQL transactions. As per my knowledge, there could be two solutions to maintain sync between index and database effectively. -- There'd be a *huge number of transactions (DMLs) on the DB*, so I'm wondering which one of the following will be able to handle it effectively. 1) Configure *Solr *server, query it to search / send events to update. This might be better than handling Lucene solely which provides index read/write and load balancing. The problem here could be to implement maintain sync between index and DB with no lag as the updations (DMLs on DB) are very frequent. Too many events to be sent! 2) Using *Hibernate Search*. I'm just wondering about its *performance*considering high volume of transactions on DB every minute. Please suggest. Thanks in advance.
Solr vs Hibernate Search (Huge number of DB DMLs)
Hi all, There were several places I could find a discussion on this but I failed to find the suited one for me. I'd like to be clear on my requirements, so that you may suggest me the better solution. - A project deals with tons of database tables (with *millions *of records) out of which some are to be indexed which should be searchable of-course. It uses Hibernate for MySQL transactions. As per my knowledge, there could be two solutions to maintain sync between index and database effectively. -- There'd be a *huge number of transactions (DMLs) on the DB*, so I'm wondering which one of the following will be able to handle it effectively. 1) Configure *Solr *server, query it to search / send events to update. This might be better than handling Lucene solely which provides index read/write and load balancing. The problem here could be to implement maintain sync between index and DB with no lag as the updations (DMLs on DB) are very frequent. Too many events to be sent! 2) Using *Hibernate Search*. I'm just wondering about its *performance*considering high volume of transactions on DB every minute. Please suggest. Thanks in advance.
Re: Solr vs Hibernate Search (Huge number of DB DMLs)
From my exploration so far, I understood that we can opt Solr straightaway if the index changes are kept to minimal. However, mine is absolutely the opposite. I'm still vague about the perfect solution for the scenario mentioned. Please share.. On Mon, Jul 4, 2011 at 6:28 PM, fire fox fyr3...@gmail.com wrote: Hi all, There were several places I could find a discussion on this but I failed to find the suited one for me. I'd like to be clear on my requirements, so that you may suggest me the better solution. - A project deals with tons of database tables (with *millions *of records) out of which some are to be indexed which should be searchable of-course. It uses Hibernate for MySQL transactions. As per my knowledge, there could be two solutions to maintain sync between index and database effectively. -- There'd be a *huge number of transactions (DMLs) on the DB*, so I'm wondering which one of the following will be able to handle it effectively. 1) Configure *Solr *server, query it to search / send events to update. This might be better than handling Lucene solely which provides index read/write and load balancing. The problem here could be to implement maintain sync between index and DB with no lag as the updations (DMLs on DB) are very frequent. Too many events to be sent! 2) Using *Hibernate Search*. I'm just wondering about its *performance*considering high volume of transactions on DB every minute. Please suggest. Thanks in advance.
Re: SOLR or Hibernate Search?
Hi! Thanks for the answers. These were crucial to my decision. I've adapted the solr in my application. On Wed, Dec 30, 2009 at 2:00 AM, Ryan McKinley ryan...@gmail.com wrote: If you need to search via the Hibernate API, then use hibernate search. If you need a scaleable HTTP (REST) then solr may be the way to go. Also, i don't think hibernate has anything like the faceting / complex query stuff etc. On Dec 29, 2009, at 3:25 PM, Márcio Paulino wrote: Hey Everyone! I was make a comparison of both technologies (SOLR AND Hibernate Search) and i see many things are equals. Anyone could told me when i must use SOLR and when i must use Hibernate Search? Im my project i will have: 1. Queries for indexed fields (Strings) and for not indexed Fields (Integer, Float, Date). [In Hibernate Search on in SOLR, i must search on index and, with results of query, search on database (I can't search in both places ate same time).] I Will Have search like: Give me all Register Where Value 190 And Name Contains = 'JAVA' 2. My client need process a lot of email (20.000 per day) and i must indexed all fields (excluded sentDate ) included Attachments, and performance is requirement of my System 3. My Application is multiclient, and i need to separate the index by client. In this Scenario, whats the best solution? SOLR or HIbernateSearch I See SOLR is a dedicated server and has a good performance test. I don't see advantages to use hibernate-search in comparison with SOLR (Except the fact of integrate with my Mapped Object) Thanks for Help -- att, ** Márcio Paulino Campo Grande - MS MSN / Gtalk: mcopaul...@gmail.com ICQ: 155897898 ** -- att, ** Márcio Paulino Campo Grande - MS MSN / Gtalk: mcopaul...@gmail.com ICQ: 155897898 **
SOLR or Hibernate Search?
Hey Everyone! I was make a comparison of both technologies (SOLR AND Hibernate Search) and i see many things are equals. Anyone could told me when i must use SOLR and when i must use Hibernate Search? Im my project i will have: 1. Queries for indexed fields (Strings) and for not indexed Fields (Integer, Float, Date). [In Hibernate Search on in SOLR, i must search on index and, with results of query, search on database (I can't search in both places ate same time).] I Will Have search like: Give me all Register Where Value 190 And Name Contains = 'JAVA' 2. My client need process a lot of email (20.000 per day) and i must indexed all fields (excluded sentDate ) included Attachments, and performance is requirement of my System 3. My Application is multiclient, and i need to separate the index by client. In this Scenario, whats the best solution? SOLR or HIbernateSearch I See SOLR is a dedicated server and has a good performance test. I don't see advantages to use hibernate-search in comparison with SOLR (Except the fact of integrate with my Mapped Object) Thanks for Help -- att, ** Márcio Paulino Campo Grande - MS MSN / Gtalk: mcopaul...@gmail.com ICQ: 155897898 **
Re: SOLR or Hibernate Search?
hi, hibernate search is only work with hibernate, while solr can use for difference system other then hibernate (loose coupling) current solr still not support complex POJO index like what hibernate did. 1) I think one way u can do is index on solr and retrieve the unique id and get from database. e.g. select enetity form table where id in (x, y) 2) i not yet test out, but i do believe lucene performance is quite good and it still keep improving (u can add more search server if u using solr) 3) maybe solr is more suitable in u case. hope this help kiwi 2009/12/30 Márcio Paulino mcopaul...@gmail.com Hey Everyone! I was make a comparison of both technologies (SOLR AND Hibernate Search) and i see many things are equals. Anyone could told me when i must use SOLR and when i must use Hibernate Search? Im my project i will have: 1. Queries for indexed fields (Strings) and for not indexed Fields (Integer, Float, Date). [In Hibernate Search on in SOLR, i must search on index and, with results of query, search on database (I can't search in both places ate same time).] I Will Have search like: Give me all Register Where Value 190 And Name Contains = 'JAVA' 2. My client need process a lot of email (20.000 per day) and i must indexed all fields (excluded sentDate ) included Attachments, and performance is requirement of my System 3. My Application is multiclient, and i need to separate the index by client. In this Scenario, whats the best solution? SOLR or HIbernateSearch I See SOLR is a dedicated server and has a good performance test. I don't see advantages to use hibernate-search in comparison with SOLR (Except the fact of integrate with my Mapped Object) Thanks for Help -- att, ** Márcio Paulino Campo Grande - MS MSN / Gtalk: mcopaul...@gmail.com ICQ: 155897898 **
Re: SOLR or Hibernate Search?
If you need to search via the Hibernate API, then use hibernate search. If you need a scaleable HTTP (REST) then solr may be the way to go. Also, i don't think hibernate has anything like the faceting / complex query stuff etc. On Dec 29, 2009, at 3:25 PM, Márcio Paulino wrote: Hey Everyone! I was make a comparison of both technologies (SOLR AND Hibernate Search) and i see many things are equals. Anyone could told me when i must use SOLR and when i must use Hibernate Search? Im my project i will have: 1. Queries for indexed fields (Strings) and for not indexed Fields (Integer, Float, Date). [In Hibernate Search on in SOLR, i must search on index and, with results of query, search on database (I can't search in both places ate same time).] I Will Have search like: Give me all Register Where Value 190 And Name Contains = 'JAVA' 2. My client need process a lot of email (20.000 per day) and i must indexed all fields (excluded sentDate ) included Attachments, and performance is requirement of my System 3. My Application is multiclient, and i need to separate the index by client. In this Scenario, whats the best solution? SOLR or HIbernateSearch I See SOLR is a dedicated server and has a good performance test. I don't see advantages to use hibernate-search in comparison with SOLR (Except the fact of integrate with my Mapped Object) Thanks for Help -- att, ** Márcio Paulino Campo Grande - MS MSN / Gtalk: mcopaul...@gmail.com ICQ: 155897898 **
