Deleting Terms:
Hi,
How to delete the terms associated with the document ?
Current scenario: We are deleting documents based on a query
('field:value').
The documents are getting deleted, however, the old terms associated to the
field are displayed in the admin.
How do we make SOLR to re-evaluate and update the terms associated to a
specific fields or latest updated document ?
(I am assuming we are missing some api calls .)
Thank you.
Kumar_/|\_
www.saisk.com
ku...@saisk.com
making a profound difference with knowledge and creativity...
Re: Deleting Terms:
BTW, Using SOLRJ - javabin api.
Kumar_/|\_
www.saisk.com
ku...@saisk.com
making a profound difference with knowledge and creativity...
On Tue, Jul 6, 2010 at 11:43 AM, Kumaravel Kandasami
kumaravel.kandas...@gmail.com wrote:
Hi,
How to delete the terms associated with the document ?
Current scenario: We are deleting documents based on a query
('field:value').
The documents are getting deleted, however, the old terms associated to the
field are displayed in the admin.
How do we make SOLR to re-evaluate and update the terms associated to a
specific fields or latest updated document ?
(I am assuming we are missing some api calls .)
Thank you.
Kumar_/|\_
www.saisk.com
ku...@saisk.com
making a profound difference with knowledge and creativity...
Re: Deleting Terms:
FYI - optimise() operations solved the issue.
Kumar_/|\_
www.saisk.com
ku...@saisk.com
making a profound difference with knowledge and creativity...
On Tue, Jul 6, 2010 at 11:47 AM, Kumaravel Kandasami
kumaravel.kandas...@gmail.com wrote:
BTW, Using SOLRJ - javabin api.
Kumar_/|\_
www.saisk.com
ku...@saisk.com
making a profound difference with knowledge and creativity...
On Tue, Jul 6, 2010 at 11:43 AM, Kumaravel Kandasami
kumaravel.kandas...@gmail.com wrote:
Hi,
How to delete the terms associated with the document ?
Current scenario: We are deleting documents based on a query
('field:value').
The documents are getting deleted, however, the old terms associated to
the field are displayed in the admin.
How do we make SOLR to re-evaluate and update the terms associated to a
specific fields or latest updated document ?
(I am assuming we are missing some api calls .)
Thank you.
Kumar_/|\_
www.saisk.com
ku...@saisk.com
making a profound difference with knowledge and creativity...
Re: Complex relational values
I would represent each item element as a document, and each attribute as the fields of the document. if the field names are not known upfront, you could create 'dynamic fields'. Kumar_/|\_ www.saisk.com ku...@saisk.com making a profound difference with knowledge and creativity... On Fri, Mar 26, 2010 at 12:37 PM, Phil Messenger p...@miniweb.tv wrote: Hi, I need to store structured information in an index entry for use when filtering. As XML, this could be expressed as: item some_fields_that_are_searched_using_dismax / data item type=foo x=100 y=200 / item type=bar x=300 y=1000 / /data /item I want to be able to *filter* search results according to the data in the item tags - eg. show all index entries which match the expression type=foo x 100 y 500 Having a multivalued field for type, x and y doesn't seem to work here as I need to maintain the relationship between a type/x/y. I'm not sure how to approach this problem. Is writing a custom field type the preferred approach? thanks, Phil.
Retrieve Field Names:
How to retrieve field names from the dynamic schema in the client side program ? Any links or reference would be helpful. (Similar to the schema browser on the SOLR admin screen.) Kumar_/|\_ www.saisk.com ku...@saisk.com making a profound difference with knowledge and creativity...
Re: Design Question - Dynamic Field Names (*)
First Thanks for the response. Yes, mostly likely we want to optimize to one index file. I think it is possible, coming from the RDBMS world we might be over complicating the solution. *Requirement:* - We are indexing CSV files and generating field names dynamically from the header line. User should be able to *list all the possible header names* (i.e. dynamic field names), and filter results based on some of the field names. - Also, list* all possible values* associated to for a given field name. Kumar_/|\_ www.saisk.com ku...@saisk.com making a profound difference with knowledge and creativity... On Tue, Jan 19, 2010 at 1:33 PM, Shalin Shekhar Mangar shalinman...@gmail.com wrote: On Sat, Jan 16, 2010 at 3:33 AM, Kumaravel Kandasami kumaravel.kandas...@gmail.com wrote: Need to your suggestion in best designing the following requirement. - We have two indexes. Index 1: name_index, Fields: id - indexed, not stored field_name - indexed, stored. Index 2: trans_index', Fields(Dynamic Schema): id - indexed, not stored * - indexed, stored. (Dynamic field names of the trans_index is the same as the field_name from the name_index.) - Requirement: User would select the field he wants to query from the name_index. Once he selects the one of the values from the 'field_name' (from the name_index), he queries the trans_index using the field_name. - Issue: When indexing the name_index field:field_name we are using the analyzer that would lowercase, strip spaces etc. Example: First Name, firstName values are all stored and indexed as 'firstname'. However, when we store field names in the trans_index we would be storing as it is ... without analyzing. So User queries like 'firstname:a*' might not match. - Possible Solution: We are planning to have an custom analyzer that we would use while indexing (configured in the schema.xml) file. As well the crawler program would use the same analyzer to create field names. Is there any better design solutions ? Your scenario sounds quite strange and it is still not clear why you are doing all this. Perhaps the solution doesn't even require two indexes? Can you describe the actual problem so that we can be of more help? -- Regards, Shalin Shekhar Mangar.
Design Question - Dynamic Field Names (*)
Need to your suggestion in best designing the following requirement. - We have two indexes. Index 1: name_index, Fields: id - indexed, not stored field_name - indexed, stored. Index 2: trans_index', Fields(Dynamic Schema): id - indexed, not stored * - indexed, stored. (Dynamic field names of the trans_index is the same as the field_name from the name_index.) - Requirement: User would select the field he wants to query from the name_index. Once he selects the one of the values from the 'field_name' (from the name_index), he queries the trans_index using the field_name. - Issue: When indexing the name_index field:field_name we are using the analyzer that would lowercase, strip spaces etc. Example: First Name, firstName values are all stored and indexed as 'firstname'. However, when we store field names in the trans_index we would be storing as it is ... without analyzing. So User queries like 'firstname:a*' might not match. - Possible Solution: We are planning to have an custom analyzer that we would use while indexing (configured in the schema.xml) file. As well the crawler program would use the same analyzer to create field names. Is there any better design solutions ? Kumar_/|\_ www.saisk.com ku...@saisk.com making a profound difference with knowledge and creativity...
