multivalue

Solr, how to use the new field update modes (atomic updates) with SolrJ

你说的曾经没有我的故事 提交于 2019-12-10 10:26:53
问题 Solr 4.x has this nice new feature that lets you specify how, when doing an update on an existing document, the multiValued fields will be updated. Specifically, you can say if the update document will replace the old values of a multivalued field with the new ones, or if it should append the new values to the existing ones. I've tried this using the request handler, as described here: http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22field.22 I've used curl to send xml

Is there a way to query multiple hash keys in DynamoDB?

半世苍凉 提交于 2019-12-09 08:21:44
问题 Is there a way to query multiple hash keys using a single query in Amazon's AWS SDK for Java? Here's my issue; I have a DB table for project statuses. The Hash Key is the status of a project (ie: new, assigned, processing, or complete). The range key is a set of project IDs. Currently, I've got a query setup to simply find all the projects listed as a status(hash) of "assigned" and another query set to look for a status of "processing". Is there a way to do this using a single query rather

Appending Multi-value lists

▼魔方 西西 提交于 2019-12-08 07:31:16
问题 I have an Access 2007 data entry form that is bound to a table that is used solely as a holding station for the data until it is reviewed and appended to the permanent tables. There are several fields in the table (and thus form) that have multi-value selections (derived from a look-up table query). The user does not care if the data is searchable so storing in the text field as a long list is fine. The problem is with appending. I cannot append multi-value lists to a table. I noticed that if

Solr - DataImportHandler: When attempting to use column values as field names, multivalued fields only retain the first result

[亡魂溺海] 提交于 2019-12-08 01:01:33
问题 I'm trying to perform a full-import with document configuration similar to the following: <document> <entity name="parent" query="select * from parent_table" > <field name="id" column="ID" /> <entity name="child" query="select * from child_table where PARENT_ID = ${parent.ID}" transformer="ClobTransformer" > <field name="${child.FIELD_COLUMN}" column="VALUE_COLUMN" clob="true" /> </entity> </entity> </document> Let's say the field/value results from the child_table for parent.ID=1 look like

In Solr, can I sort on the matching value from a multi-valued field?

淺唱寂寞╮ 提交于 2019-12-07 04:23:28
问题 We are considering a schema with two multi-valued fields. Search is performed on the first field, but sorting should be done on the second field, using the corresponding value. E.g. if documents match because of the n-th value in the first field (where n may be different for each match), then they should be returned sorted by the n-th value in the second field. Is that possible? Background: each document has a list of similar documents (IDs) and a corresponding list of similarity scores

Solr - DataImportHandler: When attempting to use column values as field names, multivalued fields only retain the first result

一个人想着一个人 提交于 2019-12-06 11:50:31
I'm trying to perform a full-import with document configuration similar to the following: <document> <entity name="parent" query="select * from parent_table" > <field name="id" column="ID" /> <entity name="child" query="select * from child_table where PARENT_ID = ${parent.ID}" transformer="ClobTransformer" > <field name="${child.FIELD_COLUMN}" column="VALUE_COLUMN" clob="true" /> </entity> </entity> </document> Let's say the field/value results from the child_table for parent.ID=1 look like this: FIELD_COLUMN VALUE_COLUMN fieldA value1 fieldB value2 fieldB value3 And the schema configuration

Solr, how to use the new field update modes (atomic updates) with SolrJ

独自空忆成欢 提交于 2019-12-06 03:30:26
Solr 4.x has this nice new feature that lets you specify how, when doing an update on an existing document, the multiValued fields will be updated. Specifically, you can say if the update document will replace the old values of a multivalued field with the new ones, or if it should append the new values to the existing ones. I've tried this using the request handler, as described here: http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22field.22 I've used curl to send xml where some fields used the update=add option: <field name="skills" update="add">Python</field> This

Alternative to multi-valued fields in MS Access

♀尐吖头ヾ 提交于 2019-12-04 12:29:59
问题 Related question: Multivalued Fields a Good Idea? I know that multi-valued fields are similar to many-to-many relationship. What is the best way to replace multi-valued fields in an MS Access application? I have an application that has multi-valued fields. I am not sure how exactly to do away with those and implement exactly same logic in the form of fields that are single-valued? What would be the implementation in terms of table-relationships when I want to move a multi-valued relationship

Search for document in Solr where a multivalue field is either empty or has a specific value

左心房为你撑大大i 提交于 2019-12-04 03:22:45
问题 I have a multivalue field in Solr, and want to query for documents where this field is either empty, or contains a specific value. 回答1: It's not straight forward, but this works: myField:"myValue" OR (*:* NOT myField:["" TO *]) I used Solr 5.4 to test the query, which had satisfying results: { "myField": [ "myValue" ], "id": "96c353e6" }, { "id": "8bcbe253" }, { "myField": [ "myValue", "otherValue" ], "id": "c3749005" } 来源: https://stackoverflow.com/questions/35633037/search-for-document-in

Break atomicity rule storing list of items when there is no reason to query about items? Verses join table that requires whole join table be scanned

杀马特。学长 韩版系。学妹 提交于 2019-12-04 02:35:36
问题 This specific case is regarding lists, and items. The same item may belong to multiple lists, and each list has many items. Option A (the "proper" way as I understand it): Make a join table, which has list_ID and item_ID. When I want all the items in a list query for list_ID. Option B (break the atomicity rule): Make a list table. Primary Key, and either repeating columns or non-atomic columns. As I understand it both of these deviations suffer the exact same drawbacks, which is the inability