You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2007/05/02 01:42:15 UTC
[jira] Updated: (SOLR-217) schema option to ignore unused fields
[ https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-217:
--------------------------
Attachment: ignoreUnnamedFields_v3.patch
added a simple test to the existing patch.
one thing to note is that this will result in the field being "ignored" if you try to query on it as well ... but this is a more general problem of qhat to do when people try to query on an unindexed field (see SOLR-223)
will commit in a day or so barring objections
> schema option to ignore unused fields
> -------------------------------------
>
> Key: SOLR-217
> URL: https://issues.apache.org/jira/browse/SOLR-217
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 1.2
> Reporter: Will Johnson
> Priority: Minor
> Fix For: 1.2
>
> Attachments: ignoreNonIndexedNonStoredField.patch, ignoreUnnamedFields.patch, ignoreUnnamedFields_v3.patch, ignoreUnnamedFields_v3.patch
>
>
> One thing that causes problems for me (and i assume others) is that Solr is schema-strict in that unknown fields cause solr to throw exceptions and there is no way to relax this constraint. this can cause all sorts of serious problems if you have automated feeding applications that do things like SELECT * FROM table1 or where you want to add other fields to the document for processing purposes before sending them to solr but don't want to deal with 'cleanup'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
RE: [jira] Updated: (SOLR-217) schema option to ignore unused fields
Posted by Chris Hostetter <ho...@fucit.org>.
And aparently i just replied to the wrong email, which just goes to show
i'm not in shape to run svn commit...
: as far as i'm concerned it's ready to commit ... but i've been sick, and i
: i have moral objections to using my commiter bit while:
: 1) sleep deprived
: 2) intoxicated
: 3) medicated
: 4) suffering from headaches
:
: ..since i've been 2 for 4 the past few days, i've been holding off.
...
: Any update on this? I'm one little * away from having a clean
: build/test.
:
: - will
:
: -----Original Message-----
: From: Hoss Man (JIRA) [mailto:jira@apache.org]
: Sent: Tuesday, May 01, 2007 7:42 PM
: To: solr-dev@lucene.apache.org
: Subject: [jira] Updated: (SOLR-217) schema option to ignore unused
: fields
:
:
: [
: https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.p
: lugin.system.issuetabpanels:all-tabpanel ]
:
: Hoss Man updated SOLR-217:
: --------------------------
:
: Attachment: ignoreUnnamedFields_v3.patch
:
: added a simple test to the existing patch.
:
: one thing to note is that this will result in the field being "ignored"
: if you try to query on it as well ... but this is a more general problem
: of qhat to do when people try to query on an unindexed field (see
: SOLR-223)
:
: will commit in a day or so barring objections
:
: > schema option to ignore unused fields
: > -------------------------------------
: >
: > Key: SOLR-217
: > URL: https://issues.apache.org/jira/browse/SOLR-217
: > Project: Solr
: > Issue Type: Improvement
: > Components: update
: > Affects Versions: 1.2
: > Reporter: Will Johnson
: > Priority: Minor
: > Fix For: 1.2
: >
: > Attachments: ignoreNonIndexedNonStoredField.patch,
: ignoreUnnamedFields.patch, ignoreUnnamedFields_v3.patch,
: ignoreUnnamedFields_v3.patch
: >
: >
: > One thing that causes problems for me (and i assume others) is that
: Solr is schema-strict in that unknown fields cause solr to throw
: exceptions and there is no way to relax this constraint. this can cause
: all sorts of serious problems if you have automated feeding applications
: that do things like SELECT * FROM table1 or where you want to add other
: fields to the document for processing purposes before sending them to
: solr but don't want to deal with 'cleanup'
:
: --
: This message is automatically generated by JIRA.
: -
: You can reply to this email to add a comment to the issue online.
:
-Hoss
RE: [jira] Updated: (SOLR-217) schema option to ignore unused fields
Posted by Will Johnson <wj...@GETCONNECTED.COM>.
Any update on this? I'm one little * away from having a clean
build/test.
- will
-----Original Message-----
From: Hoss Man (JIRA) [mailto:jira@apache.org]
Sent: Tuesday, May 01, 2007 7:42 PM
To: solr-dev@lucene.apache.org
Subject: [jira] Updated: (SOLR-217) schema option to ignore unused
fields
[
https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.p
lugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-217:
--------------------------
Attachment: ignoreUnnamedFields_v3.patch
added a simple test to the existing patch.
one thing to note is that this will result in the field being "ignored"
if you try to query on it as well ... but this is a more general problem
of qhat to do when people try to query on an unindexed field (see
SOLR-223)
will commit in a day or so barring objections
> schema option to ignore unused fields
> -------------------------------------
>
> Key: SOLR-217
> URL: https://issues.apache.org/jira/browse/SOLR-217
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 1.2
> Reporter: Will Johnson
> Priority: Minor
> Fix For: 1.2
>
> Attachments: ignoreNonIndexedNonStoredField.patch,
ignoreUnnamedFields.patch, ignoreUnnamedFields_v3.patch,
ignoreUnnamedFields_v3.patch
>
>
> One thing that causes problems for me (and i assume others) is that
Solr is schema-strict in that unknown fields cause solr to throw
exceptions and there is no way to relax this constraint. this can cause
all sorts of serious problems if you have automated feeding applications
that do things like SELECT * FROM table1 or where you want to add other
fields to the document for processing purposes before sending them to
solr but don't want to deal with 'cleanup'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.