[jira] Commented: (SOLR-619) Register copyField at runtime

2008-08-05 Thread Yonik Seeley (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12620002#action_12620002
 ] 

Yonik Seeley commented on SOLR-619:
---

Can this issue be closed?

 Register copyField at runtime
 -

 Key: SOLR-619
 URL: https://issues.apache.org/jira/browse/SOLR-619
 Project: Solr
  Issue Type: New Feature
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Priority: Minor
 Fix For: 1.3

 Attachments: SOLR-619-RuntimeSchema.patch, 
 SOLR-619-RuntimeSchema.patch, SOLR-619.patch


 In order to enable runtime schema manipulation, it would be nice to register 
 copy fields manually rather then requiring them to be registered via 
 schema.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-619) Register copyField at runtime

2008-07-18 Thread Yonik Seeley (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614734#action_12614734
 ] 

Yonik Seeley commented on SOLR-619:
---

Noble - I don't think your variation is thread safe.  I don't believe it can be 
without some level of synchronization or volatile on the read-side.  Since a 
truly thread-safe implementation requires slowing down the read-side,  I think 
adding copyFields should (for now) be restricted to use before or during the 
inform() phase.

 Register copyField at runtime
 -

 Key: SOLR-619
 URL: https://issues.apache.org/jira/browse/SOLR-619
 Project: Solr
  Issue Type: New Feature
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Priority: Minor
 Fix For: 1.3

 Attachments: SOLR-619-RuntimeSchema.patch, SOLR-619.patch


 In order to enable runtime schema manipulation, it would be nice to register 
 copy fields manually rather then requiring them to be registered via 
 schema.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-619) Register copyField at runtime

2008-07-18 Thread Noble Paul (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614814#action_12614814
 ] 

Noble Paul commented on SOLR-619:
-

If the fields are made volatile , should it be ok? How expensive are volatile 
fields?

bq.I think adding copyFields should (for now) be restricted to use before or 
during the inform() phase.

I would g w/ this approach.Making reads expensive is *not an option*.  

 Register copyField at runtime
 -

 Key: SOLR-619
 URL: https://issues.apache.org/jira/browse/SOLR-619
 Project: Solr
  Issue Type: New Feature
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Priority: Minor
 Fix For: 1.3

 Attachments: SOLR-619-RuntimeSchema.patch, SOLR-619.patch


 In order to enable runtime schema manipulation, it would be nice to register 
 copy fields manually rather then requiring them to be registered via 
 schema.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (SOLR-619) Register copyField at runtime

2008-07-07 Thread Yonik Seeley (JIRA)

[ 
https://issues.apache.org/jira/browse/SOLR-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12611277#action_12611277
 ] 

Yonik Seeley commented on SOLR-619:
---

This patch has thread safety issues if the new API were to be used from more 
than one thread, or concurrently with searching.

 Register copyField at runtime
 -

 Key: SOLR-619
 URL: https://issues.apache.org/jira/browse/SOLR-619
 Project: Solr
  Issue Type: New Feature
Reporter: Ryan McKinley
Assignee: Ryan McKinley
Priority: Minor
 Fix For: 1.3

 Attachments: SOLR-619-RuntimeSchema.patch


 In order to enable runtime schema manipulation, it would be nice to register 
 copy fields manually rather then requiring them to be registered via 
 schema.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.