[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15027487#comment-15027487
]
Dominik Siebel commented on SOLR-7169:
--
Thanks for merging this, Timothy.
This will then be fixed with 5.4.0 I assume?
Will there be another 5.3.x before that?
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
> Fix For: 5.4
>
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15027515#comment-15027515
]
Dominik Siebel commented on SOLR-7169:
--
[~upayavira] Excellent, Thanks!
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
> Fix For: 5.4
>
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021774#comment-15021774
]
Dominik Siebel commented on SOLR-7169:
--
Since this task seems to be "IN PROGRESS" already: I have a patched, working
version of the solr run script that I use in our setup. Anybody interested in
that?
[~tpot], [~m...@addwish.com]
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15021939#comment-15021939
]
Dominik Siebel commented on SOLR-7169:
--
[~ichattopadhyaya] Thanks, it's not my first change ;)
Is it already possible to provide patches via GitHub Pull Requests?
I saw a couple of them being opened and integrated by committers manually...
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022065#comment-15022065
]
Dominik Siebel commented on SOLR-7169:
--
Seems like it works :D
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022370#comment-15022370
]
Dominik Siebel commented on SOLR-7169:
--
[~ichattopadhyaya] Sure, I will give it another try.
I also realized that it's not yet working in all cases because the script forks
subshells to read the pid files for example.
I will provide another changeset that hopefully covers all of them.
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022394#comment-15022394
]
Dominik Siebel edited comment on SOLR-7169 at 11/23/15 4:28 PM:
New patch: https://github.com/apache/lucene-solr/pull/212.patch
I threw away all previous changes and combined everything into one commit.
The subshell problem seems to be solved but there is still on minor issue
remaining:
If there are running Solr instances the return value of {{get_info}} will
always be the return value of the last {{run_tool status}} call since all
available pid files / running processes are processed in a loop.
This is fine for single-node setups but might lead to side effects on
multi-node setups (multiple instances / services running on one machine).
was (Author: dsiebel):
New patch: https://github.com/apache/lucene-solr/pull/212.patch
I threw away all previous changes and combined everything into one commit.
The subshell problem seems to be solved but there is still on minor issue
remaining:
If there are running Solr instances the return value of {{get_info}} will
always be the outcome of the last call to {{run_tool status}} since all pid
files / running processes are processed in a loop.
This is fine for single-node setups but might lead to side effects on
multi-node setups (multiple instances / services running on one machine).
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022394#comment-15022394
]
Dominik Siebel commented on SOLR-7169:
--
New patch: https://github.com/apache/lucene-solr/pull/212.patch
I threw away all previous changes and combined everything into one commit.
The subshell problem seems to be solved but there is still on minor issue
remaining:
If there are running Solr instances the return value of {{get_info}} will
always be the outcome of the last call to {{run_tool status}} since all pid
files / running processes are processed in a loop.
This is fine for single-node setups but might lead to side effects on
multi-node setups (multiple instances / services running on one machine).
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022217#comment-15022217
]
Dominik Siebel commented on SOLR-7169:
--
As it turns out following the LSB standard and returning 3 if the service is
not running does not fix the problem with saltstack orchestration (returning 1
however does).
Does it fix the problem for Puppet? Any chance you could test the patch,
[~m...@addwish.com]?
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022394#comment-15022394
]
Dominik Siebel edited comment on SOLR-7169 at 11/23/15 9:01 PM:
New patch: https://github.com/apache/lucene-solr/pull/212.patch
I threw away all previous changes and combined everything into one commit.
The subshell problem seems to be solved but there is still one minor issue
remaining:
If there are running Solr instances the return value of {{get_info}} will
always be the return value of the last {{run_tool status}}-call since all
available pid files / running processes are processed in a loop.
This is fine for single-node setups but might lead to side effects on
multi-node setups (multiple instances / services running on one machine).
was (Author: dsiebel):
New patch: https://github.com/apache/lucene-solr/pull/212.patch
I threw away all previous changes and combined everything into one commit.
The subshell problem seems to be solved but there is still on minor issue
remaining:
If there are running Solr instances the return value of {{get_info}} will
always be the return value of the last {{run_tool status}} call since all
available pid files / running processes are processed in a loop.
This is fine for single-node setups but might lead to side effects on
multi-node setups (multiple instances / services running on one machine).
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7169) init.d status command has incorrect return value
[
https://issues.apache.org/jira/browse/SOLR-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15016698#comment-15016698
]
Dominik Siebel commented on SOLR-7169:
--
Experiencing the same problem with orchestration via Saltstack currently.
> init.d status command has incorrect return value
>
>
> Key: SOLR-7169
> URL: https://issues.apache.org/jira/browse/SOLR-7169
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
>Affects Versions: 5.0
> Environment: Debian stable
>Reporter: Martin Skøtt
>Assignee: Timothy Potter
>
> {{/etc/init.d/solr status}} returns 0 if Solr is not running, but according
> to the LSB 0 means that the service is running
> (http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
> In my situation this causes problems when managing the service with Puppet
> which uses the status command to determine if a service should be started.
> Puppet simply doesn't start the service because it thinks its already
> running. Any other script depending on the result of the status command will
> suffer similar problems.
> Workaround for other Puppet users:
> Setting {{hasstatus => false}} and {{pattern => "solr.solr.home"}} in the
> service definition works for me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5931) solrcore.properties is not reloaded when core is reloaded
[
https://issues.apache.org/jira/browse/SOLR-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14043093#comment-14043093
]
Dominik Siebel commented on SOLR-5931:
--
Addition: It also seems that properties linked via solr.xml core attribute
properties are not reloading anymore (version 4.6).
I used to use this file to dynamically enable/disable replication for specific
nodes and reload the core. Now I have to restart the whole Node.
This definitely worked before (version 4.3) Does this qualify as a bug
[~shalinmangar] ? ;)
solrcore.properties is not reloaded when core is reloaded
-
Key: SOLR-5931
URL: https://issues.apache.org/jira/browse/SOLR-5931
Project: Solr
Issue Type: Bug
Components: multicore
Affects Versions: 4.7
Reporter: Gunnlaugur Thor Briem
Assignee: Shalin Shekhar Mangar
Priority: Minor
When I change solrcore.properties for a core, and then reload the core, the
previous values of the properties in that file are still in effect. If I
*unload* the core and then add it back, in the “Core Admin” section of the
admin UI, then the changes in solrcore.properties do take effect.
My specific test case is a DataImportHandler where {{db-data-config.xml}}
uses a property to decide which DB host to talk to:
{code:xml}
dataSource driver=org.postgresql.Driver name=meta
url=jdbc:postgresql://${dbhost}/${solr.core.name} .../
{code}
When I change that {{dbhost}} property in {{solrcore.properties}} and reload
the core, the next dataimport operation still connects to the previous DB
host. Reloading the dataimport config does not help. I have to unload the
core (or fully restart the whole Solr) for the properties change to take
effect.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5190) SolrEntityProcessor substitutes variables only once in child entities
[ https://issues.apache.org/jira/browse/SOLR-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895890#comment-13895890 ] Dominik Siebel commented on SOLR-5190: -- [~shalinmangar], [~jpountz] Is there any chance, this will be merged to branch lucene_solr_4_3 / lucene_solr_4_4 ? SolrEntityProcessor substitutes variables only once in child entities - Key: SOLR-5190 URL: https://issues.apache.org/jira/browse/SOLR-5190 Project: Solr Issue Type: Bug Components: contrib - DataImportHandler Affects Versions: 4.4 Reporter: Shalin Shekhar Mangar Assignee: Shalin Shekhar Mangar Priority: Minor Fix For: 4.5, 5.0 Attachments: SOLR-5190.patch As noted by users on the mailing list and elsewhere, SolrEntityProcessor cannot be used in a child entity because it substitutes variables only once. http://www.mail-archive.com/solr-user@lucene.apache.org/msg88002.html http://stackoverflow.com/questions/15734308/solrentityprocessor-is-called-only-once-for-sub-entities?lq=1 SOLR-3336 attempted to fix the problem by moving variable substitution to the doQuery method but that fix is not complete because the doQuery method is called only once. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5190) SolrEntityProcessor substitutes variables only once in child entities
[ https://issues.apache.org/jira/browse/SOLR-5190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13895959#comment-13895959 ] Dominik Siebel commented on SOLR-5190: -- [~steamedcotton] Already did (forked github mirror). Just thought it would be nice to have it in the upstream. Thanks for the reply! SolrEntityProcessor substitutes variables only once in child entities - Key: SOLR-5190 URL: https://issues.apache.org/jira/browse/SOLR-5190 Project: Solr Issue Type: Bug Components: contrib - DataImportHandler Affects Versions: 4.4 Reporter: Shalin Shekhar Mangar Assignee: Shalin Shekhar Mangar Priority: Minor Fix For: 4.5, 5.0 Attachments: SOLR-5190.patch As noted by users on the mailing list and elsewhere, SolrEntityProcessor cannot be used in a child entity because it substitutes variables only once. http://www.mail-archive.com/solr-user@lucene.apache.org/msg88002.html http://stackoverflow.com/questions/15734308/solrentityprocessor-is-called-only-once-for-sub-entities?lq=1 SOLR-3336 attempted to fix the problem by moving variable substitution to the doQuery method but that fix is not complete because the doQuery method is called only once. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4086) Refactor DIH - VariableResolver Evaluator
[ https://issues.apache.org/jira/browse/SOLR-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13660408#comment-13660408 ] Dominik Siebel commented on SOLR-4086: -- [~jdyer] just FYI. I jut had time to check integration of 4.3 (build from github mirror branch) into our environment and DIH runtimes seem to be back to normal. Good Work! Refactor DIH - VariableResolver Evaluator --- Key: SOLR-4086 URL: https://issues.apache.org/jira/browse/SOLR-4086 Project: Solr Issue Type: Improvement Components: contrib - DataImportHandler Affects Versions: 4.0 Reporter: James Dyer Assignee: James Dyer Priority: Minor Fix For: 4.1, 5.0 Attachments: SOLR-4086.patch This simplifies VariableResolver and moves each built-in Evaluator into its own class. Compiler warnings / missing generics are fixed. Also, the Locale bug with DateFormatEvaluator is solved. Instead of using the machine default, the Root Locale is used by default. An optional 3rd parameter allows users to specify whatever locale they want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4086) Refactor DIH - VariableResolver Evaluator
[ https://issues.apache.org/jira/browse/SOLR-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13596927#comment-13596927 ] Dominik Siebel commented on SOLR-4086: -- Hi [~jdyer], sorry I haven't looked into this for quite some time now. We already decided to postponed the Solr4 update which is why I had to work on other tasks for the last months. I will definitely look into this again when the time has come. Refactor DIH - VariableResolver Evaluator --- Key: SOLR-4086 URL: https://issues.apache.org/jira/browse/SOLR-4086 Project: Solr Issue Type: Improvement Components: contrib - DataImportHandler Affects Versions: 4.0 Reporter: James Dyer Assignee: James Dyer Priority: Minor Fix For: 4.1, 5.0 Attachments: SOLR-4086.patch This simplifies VariableResolver and moves each built-in Evaluator into its own class. Compiler warnings / missing generics are fixed. Also, the Locale bug with DateFormatEvaluator is solved. Instead of using the machine default, the Root Locale is used by default. An optional 3rd parameter allows users to specify whatever locale they want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4086) Refactor DIH - VariableResolver Evaluator
[
https://issues.apache.org/jira/browse/SOLR-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13536873#comment-13536873
]
Dominik Siebel commented on SOLR-4086:
--
Hi James,
thanks for the quick reply.
I will have to check if company policy allows to post our data-config xmls in a
public issue tracker, but I can say that much:
our data-configs mainly consist of nested entities using variables to access
the parent scope and also using the ${dataimporter.function.escapeSql()}
function to strip unwanted characters. Nothing more ( no DateFormatEvaluator,
at least not explicitly ).
The query results of the root entity are post-processed via ScriptTransformer.
The JVM is
* Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM (1.6.0_37 20.12-b01)
Configured with
* -d64
* -Xms8g
* -Xmx8g
* -XX:+CMSParallelRemarkEnabled
* -XX:+UseConcMarkSweepGC
* -XX:+UseParNewGC
With cores
* main (~17G)
Refactor DIH - VariableResolver Evaluator
---
Key: SOLR-4086
URL: https://issues.apache.org/jira/browse/SOLR-4086
Project: Solr
Issue Type: Improvement
Components: contrib - DataImportHandler
Affects Versions: 4.0
Reporter: James Dyer
Assignee: James Dyer
Priority: Minor
Fix For: 4.1, 5.0
Attachments: SOLR-4086.patch
This simplifies VariableResolver and moves each built-in Evaluator into its
own class. Compiler warnings / missing generics are fixed. Also, the Locale
bug with DateFormatEvaluator is solved. Instead of using the machine
default, the Root Locale is used by default. An optional 3rd parameter
allows users to specify whatever locale they want.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4086) Refactor DIH - VariableResolver Evaluator
[ https://issues.apache.org/jira/browse/SOLR-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13536089#comment-13536089 ] Dominik Siebel commented on SOLR-4086: -- [~jdyer] I noticed a massive decrease in indexing performance when trying a current checkout from branch_4x after this refactoring. Do you have any explanation for that? Looking through the code I could not find any changes that would explain this. *Some numbers:* * 1.3M documents * 4 DIHs *before* (with my patch from SOLR-2141): * DIH_1: documents processed: 325130, time taken: 00:25:44.445 * DIH_2: documents processed: 207347, time taken: 01:16:04.607 * DIH_3: documents processed: 184601, time taken: 01:18:00.797 * DIH_4: documents processed: 618580, time taken: 04:17:38.414 *after*: * DIH_1: documents processed: 324996, time taken: 01:07:47.186 * DIH_2: documents processed: 207347, time taken: 03:31:21.345 * DIH_3: documents processed: 184521, time taken: 03:13:11.313 * DIH_4: documents processed: 618491, time taken: 06:42:54.384 Any idea? Refactor DIH - VariableResolver Evaluator --- Key: SOLR-4086 URL: https://issues.apache.org/jira/browse/SOLR-4086 Project: Solr Issue Type: Improvement Components: contrib - DataImportHandler Affects Versions: 4.0 Reporter: James Dyer Assignee: James Dyer Priority: Minor Fix For: 4.1, 5.0 Attachments: SOLR-4086.patch This simplifies VariableResolver and moves each built-in Evaluator into its own class. Compiler warnings / missing generics are fixed. Also, the Locale bug with DateFormatEvaluator is solved. Instead of using the machine default, the Root Locale is used by default. An optional 3rd parameter allows users to specify whatever locale they want. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-4110) Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter
[ https://issues.apache.org/jira/browse/SOLR-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Siebel updated SOLR-4110: - Attachment: SOLR-4110_trunk.patch SOLR-4110_branch_4x.patch Patch to make Content-Type header configurable in PHPResponseWriters. Had to add two patches for trunk and branch_4x separately, due to changes in trunk (missing @Overrides). Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter Key: SOLR-4110 URL: https://issues.apache.org/jira/browse/SOLR-4110 Project: Solr Issue Type: Improvement Components: Response Writers Affects Versions: 4.0 Reporter: Dominik Siebel Assignee: Mark Miller Priority: Minor Labels: 4.0.1_Candidate Fix For: 4.1, 5.0 Attachments: SOLR-4110_branch_4x.patch, SOLR-4110.patch, SOLR-4110_trunk.patch The *PHPResponseWriter* and *PHPSerializedResponseWriter* currently send a hard coded Content-Type header of _text/plain; charset=UTF-8_ although there are constants defining _text/x-php;charset=UTF-8_ and _text/x-php-serialized;charset=UTF-8_ which remain unused. This makes content type guessing on the client side quite complicated. I already created a patch (from the branch_4x github branch) to use the respective constants and also added the possibility to configure the Content-Type header via solrconfig.xml (like in JSONResponseWriter). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-4110) Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter
[ https://issues.apache.org/jira/browse/SOLR-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Siebel updated SOLR-4110: - Attachment: SOLR-4110_trunk.patch SOLR-4110_branch_4x.patch Patch to make Content-Type header configurable in PHPResponseWriters. Had to add two patches for trunk and branch_4x separately, due to changes in trunk (missing @Overrides). Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter Key: SOLR-4110 URL: https://issues.apache.org/jira/browse/SOLR-4110 Project: Solr Issue Type: Improvement Components: Response Writers Affects Versions: 4.0 Reporter: Dominik Siebel Assignee: Mark Miller Priority: Minor Labels: 4.0.1_Candidate Fix For: 4.1, 5.0 Attachments: SOLR-4110_branch_4x.patch, SOLR-4110.patch, SOLR-4110_trunk.patch The *PHPResponseWriter* and *PHPSerializedResponseWriter* currently send a hard coded Content-Type header of _text/plain; charset=UTF-8_ although there are constants defining _text/x-php;charset=UTF-8_ and _text/x-php-serialized;charset=UTF-8_ which remain unused. This makes content type guessing on the client side quite complicated. I already created a patch (from the branch_4x github branch) to use the respective constants and also added the possibility to configure the Content-Type header via solrconfig.xml (like in JSONResponseWriter). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4110) Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter
[ https://issues.apache.org/jira/browse/SOLR-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13532400#comment-13532400 ] Dominik Siebel commented on SOLR-4110: -- Will do, might have to wait until Sunday, though. Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter Key: SOLR-4110 URL: https://issues.apache.org/jira/browse/SOLR-4110 Project: Solr Issue Type: Improvement Components: Response Writers Affects Versions: 4.0 Reporter: Dominik Siebel Assignee: Mark Miller Priority: Minor Labels: 4.0.1_Candidate Fix For: 4.1, 5.0 Attachments: SOLR-4110.patch The *PHPResponseWriter* and *PHPSerializedResponseWriter* currently send a hard coded Content-Type header of _text/plain; charset=UTF-8_ although there are constants defining _text/x-php;charset=UTF-8_ and _text/x-php-serialized;charset=UTF-8_ which remain unused. This makes content type guessing on the client side quite complicated. I already created a patch (from the branch_4x github branch) to use the respective constants and also added the possibility to configure the Content-Type header via solrconfig.xml (like in JSONResponseWriter). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505337#comment-13505337
]
Dominik Siebel commented on SOLR-2141:
--
Hi, James, sorry I already forgot about that. Thanks for the good work!
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1, 4.0
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: James Dyer
Fix For: 4.1, 5.0
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141.patch, SOLR-2141.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4110) Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter
[
https://issues.apache.org/jira/browse/SOLR-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506292#comment-13506292
]
Dominik Siebel commented on SOLR-4110:
--
Upgrading from 4.0?
I don't see any harm in the ResponseWriters being configurable.
JSONResponseWriter already is (as far as Content-Type header in concerned).
Sending _text/x-php;charset=UTF-8_ as default however might be an issue, yes
(if anyone really relies on text/plain for PHP and PHPs).
But since the Content-Type header of the ResponseWriters would be configurable
you could still overwrite the defaults in _solrconfig.xml_ just like the
example does with the _JSONResponseWriter_:
{code xml}
queryResponseWriter name=json class=solr.JSONResponseWriter
!-- For the purposes of the tutorial, JSON responses are written as
plain text so that they are easy to read in *any* browser.
If you expect a MIME type of application/json just remove this
override.
--
str name=content-typetext/plain; charset=UTF-8/str
/queryResponseWriter
{code}
Configurable Content-Type headers for PHPResponseWriters and
PHPSerializedResponseWriter
Key: SOLR-4110
URL: https://issues.apache.org/jira/browse/SOLR-4110
Project: Solr
Issue Type: Improvement
Components: Response Writers
Affects Versions: 4.0
Reporter: Dominik Siebel
Assignee: Mark Miller
Priority: Minor
Labels: 4.0.1_Candidate
Fix For: 4.1, 5.0
Attachments: SOLR-4110.patch
The *PHPResponseWriter* and *PHPSerializedResponseWriter* currently send a
hard coded Content-Type header of _text/plain; charset=UTF-8_ although there
are constants defining _text/x-php;charset=UTF-8_ and
_text/x-php-serialized;charset=UTF-8_ which remain unused. This makes content
type guessing on the client side quite complicated.
I already created a patch (from the branch_4x github branch) to use the
respective constants and also added the possibility to configure the
Content-Type header via solrconfig.xml (like in JSONResponseWriter).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-4110) Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter
[
https://issues.apache.org/jira/browse/SOLR-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506292#comment-13506292
]
Dominik Siebel edited comment on SOLR-4110 at 11/29/12 7:41 AM:
Upgrading from 4.0?
I don't see any harm in the ResponseWriters being configurable.
JSONResponseWriter already is (as far as Content-Type header in concerned).
Sending _text/x-php;charset=UTF-8_ as default however might be an issue, yes
(if anyone really relies on text/plain for PHP and PHPs).
But since the Content-Type header of the ResponseWriters would be configurable
you could still overwrite the defaults in _solrconfig.xml_ just like the
example does with the _JSONResponseWriter_:
{code:xml}
queryResponseWriter name=json class=solr.JSONResponseWriter
!-- For the purposes of the tutorial, JSON responses are written as
plain text so that they are easy to read in *any* browser.
If you expect a MIME type of application/json just remove this
override.
--
str name=content-typetext/plain; charset=UTF-8/str
/queryResponseWriter
{code}
was (Author: dsiebel):
Upgrading from 4.0?
I don't see any harm in the ResponseWriters being configurable.
JSONResponseWriter already is (as far as Content-Type header in concerned).
Sending _text/x-php;charset=UTF-8_ as default however might be an issue, yes
(if anyone really relies on text/plain for PHP and PHPs).
But since the Content-Type header of the ResponseWriters would be configurable
you could still overwrite the defaults in _solrconfig.xml_ just like the
example does with the _JSONResponseWriter_:
{code xml}
queryResponseWriter name=json class=solr.JSONResponseWriter
!-- For the purposes of the tutorial, JSON responses are written as
plain text so that they are easy to read in *any* browser.
If you expect a MIME type of application/json just remove this
override.
--
str name=content-typetext/plain; charset=UTF-8/str
/queryResponseWriter
{code}
Configurable Content-Type headers for PHPResponseWriters and
PHPSerializedResponseWriter
Key: SOLR-4110
URL: https://issues.apache.org/jira/browse/SOLR-4110
Project: Solr
Issue Type: Improvement
Components: Response Writers
Affects Versions: 4.0
Reporter: Dominik Siebel
Assignee: Mark Miller
Priority: Minor
Labels: 4.0.1_Candidate
Fix For: 4.1, 5.0
Attachments: SOLR-4110.patch
The *PHPResponseWriter* and *PHPSerializedResponseWriter* currently send a
hard coded Content-Type header of _text/plain; charset=UTF-8_ although there
are constants defining _text/x-php;charset=UTF-8_ and
_text/x-php-serialized;charset=UTF-8_ which remain unused. This makes content
type guessing on the client side quite complicated.
I already created a patch (from the branch_4x github branch) to use the
respective constants and also added the possibility to configure the
Content-Type header via solrconfig.xml (like in JSONResponseWriter).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503763#comment-13503763
]
Dominik Siebel commented on SOLR-2141:
--
[~jdyer]
After I finally had some time to check whether the indexed results (after the
update) are as I expect them to be I had to find out that the importer did not
throw any NPE's now, instead the fields are just missing.
I have 7 fields defined in my nested entity that use escapeSql. Those are the
exact fields that don't get indexed now :-/
Any other suggestions? ;)
I will have a look at the changed DIH code, maybe i can figure out where this
is coming from.
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503815#comment-13503815
]
Dominik Siebel commented on SOLR-2141:
--
Hi [~jdyer],
I just worked through the changes in the DIH. Turns out my fields were null,
because I used the 'dih.functions.' namespace since the
'dataimporter.functions.' was marked *_deprecated_* before the change. Did you
change that back on purpose, because it might cause some confusion (like in my
case).
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13503879#comment-13503879
]
Dominik Siebel commented on SOLR-2141:
--
Checked with
git-svn-id: https://svn.apache.org/repos/asf/lucene/dev/trunk@1413079
13f79535-47bb-0310-9956-ffa450edef68
from github trunk.
Everything seems to be running, at least the fields are present.
On optimize I get a _SEVERE: null:java.lang.NoSuchMethodError:
org.apache.lucene.document.Document.add(Lorg/apache/lucene/index/IndexableField;)V_
from the SpellChecker component, though. But this might be related to some
other issue.
I could not verify with the whole dataset yet since indexing, commit and
optimize (required for spellcheckers) take around 5h. I'll get back to you once
the import finished on our staging system.
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-4110) Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter
Dominik Siebel created SOLR-4110: Summary: Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter Key: SOLR-4110 URL: https://issues.apache.org/jira/browse/SOLR-4110 Project: Solr Issue Type: Improvement Components: Response Writers Affects Versions: 4.0 Reporter: Dominik Siebel Priority: Minor Fix For: 4.0.1 The *PHPResponseWriter* and *PHPSerializedResponseWriter* currently send a hard coded Content-Type header of _text/plain; charset=UTF-8_ although there are constants defining _text/x-php;charset=UTF-8_ and _text/x-php-serialized;charset=UTF-8_ which remain unused. This makes content type guessing on the client side quite complicated. I already created a patch (from the branch_4x github branch) to use the respective constants and also added the possibility to configure the Content-Type header via solrconfig.xml (like in JSONResponseWriter). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-4110) Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter
[ https://issues.apache.org/jira/browse/SOLR-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominik Siebel updated SOLR-4110: - Attachment: SOLR-4110.patch Configurable Content-Type headers for PHPResponseWriters and PHPSerializedResponseWriter Key: SOLR-4110 URL: https://issues.apache.org/jira/browse/SOLR-4110 Project: Solr Issue Type: Improvement Components: Response Writers Affects Versions: 4.0 Reporter: Dominik Siebel Priority: Minor Fix For: 4.0.1 Attachments: SOLR-4110.patch The *PHPResponseWriter* and *PHPSerializedResponseWriter* currently send a hard coded Content-Type header of _text/plain; charset=UTF-8_ although there are constants defining _text/x-php;charset=UTF-8_ and _text/x-php-serialized;charset=UTF-8_ which remain unused. This makes content type guessing on the client side quite complicated. I already created a patch (from the branch_4x github branch) to use the respective constants and also added the possibility to configure the Content-Type header via solrconfig.xml (like in JSONResponseWriter). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13502751#comment-13502751
]
Dominik Siebel commented on SOLR-2141:
--
[~jdyer] Thanks, this seems to have fixed my problem. I'm currently doing a
full import with a build from branch_4x, no NPEs, yet (at ~10% now).
Sorry for the (maybe) dumb question, but: is there a gonna be a stable bugfix
release or tag in the near future (not only for this issue, of course)?
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13500132#comment-13500132
]
Dominik Siebel commented on SOLR-2141:
--
/push [~vkirilchuk], [~sandeep2852], [~jdyer]
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Siebel updated SOLR-2141:
-
Attachment: SOLR-2141.patch
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Siebel updated SOLR-2141:
-
Attachment: (was: SOLR-2141.patch)
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Siebel updated SOLR-2141:
-
Attachment: SOLR-2141.patch
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13497207#comment-13497207
]
Dominik Siebel commented on SOLR-2141:
--
Hi guys,
I think I might have found the root of evil:
SOLR-3262 (removing threads from DIH). Problem is that in nested entites the
used VariableResolverImpl differs from the one used by the EvaluatorBag (since
everytime the getVariableResolver method is called a new one gets created) in
the functions namespace (since that one get's initialized in the DocBuilder
constructor).
Anyway: I removed the private functionsNamespace cache property from the
docBuilder and moved the call EvaluatorBag.getFunctionsNamespace() into
DocBuilder.getVariableResolver(). That fixes all of my problems.
[~vkirilchuk], [~sandeep2852] please find attached patch and let me know if
this fixes your errors, too.
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Siebel updated SOLR-2141:
-
Attachment: SOLR-2141.patch
Patch to fix loading of functions namespace at runtime to use the correct (the
newly created) VariableResolverImpl
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141.patch, SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Siebel updated SOLR-2141:
-
Attachment: SOLR-2141.b341f5b.patch
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496160#comment-13496160
]
Dominik Siebel commented on SOLR-2141:
--
I just added a path for commit b341f5b (github mirror of branch_4x).
Might this have caused the error?
The way I see it the EvaluatorBag looses the current context when used in a
nested entity.
The commit was executed in connection with SOLR-2542 as git log shows:
b341f5b - SOLR-2542: Fixed DIH Context variables which were broken for all
scopes other then SCOPE_ENTITY (10 months ago) Chris M. Hostetter
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496160#comment-13496160
]
Dominik Siebel edited comment on SOLR-2141 at 11/13/12 12:56 PM:
-
I just added the patch SOLR-2141.b341f5b.patch for commit b341f5b (github
mirror of branch_4x).
Might this have caused the error?
The way I see it the EvaluatorBag looses the current context when used in a
nested entity.
The commit was executed in connection with SOLR-2542 as git log shows:
b341f5b - SOLR-2542: Fixed DIH Context variables which were broken for all
scopes other then SCOPE_ENTITY (10 months ago) Chris M. Hostetter
was (Author: dsiebel):
I just added a path for commit b341f5b (github mirror of branch_4x).
Might this have caused the error?
The way I see it the EvaluatorBag looses the current context when used in a
nested entity.
The commit was executed in connection with SOLR-2542 as git log shows:
b341f5b - SOLR-2542: Fixed DIH Context variables which were broken for all
scopes other then SCOPE_ENTITY (10 months ago) Chris M. Hostetter
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141.b341f5b.patch,
SOLR-2141-sample.patch, SOLR-2141-test.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13495410#comment-13495410
]
Dominik Siebel commented on SOLR-2141:
--
I am having the exact same issue since upgrading from 4.0.0 nightly (aprox.
November 2011) to 4.0.0 stable (ans also 4.0.0 BETA).
I already tried to resolve it with the help of the Solr User's mailinglist:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201210.mbox/%3CCAAh4Jhuv86xbVa6=zdxshuw3ferum+org4pdtkqadgagefb...@mail.gmail.com%3E
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141-sample.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13495421#comment-13495421
]
Dominik Siebel commented on SOLR-2141:
--
Sadly there's no way for me to reopen this issue like [~koji] suggested.
Maybe [~urkle] can?
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141-sample.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13495410#comment-13495410
]
Dominik Siebel edited comment on SOLR-2141 at 11/12/12 5:07 PM:
I am having the exact same issue since upgrading from 4.0.0 nightly (aprox.
November 2011) to 4.0.0 stable (and previously also 4.0.0 BETA).
I already tried to resolve it with the help of the Solr User's mailinglist:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201210.mbox/%3CCAAh4Jhuv86xbVa6=zdxshuw3ferum+org4pdtkqadgagefb...@mail.gmail.com%3E
was (Author: dsiebel):
I am having the exact same issue since upgrading from 4.0.0 nightly (aprox.
November 2011) to 4.0.0 stable (ans also 4.0.0 BETA).
I already tried to resolve it with the help of the Solr User's mailinglist:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201210.mbox/%3CCAAh4Jhuv86xbVa6=zdxshuw3ferum+org4pdtkqadgagefb...@mail.gmail.com%3E
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141-sample.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-2141) NullPointerException when using escapeSql function
[
https://issues.apache.org/jira/browse/SOLR-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13495635#comment-13495635
]
Dominik Siebel commented on SOLR-2141:
--
If it helps:
I just checked for the nightly build I had in use (with DIH working fine) until
I started upgrading to 4.0.0 (beta) a few weeks ago:
apache-solr-4.0-2011-09-16_08-37-32.war
with
apache-solr-dataimporthandler-4.0-2011-09-16_08-37-32.jar
apache-solr-dataimporthandler-extras-4.0-2011-09-16_08-37-32.jar
NullPointerException when using escapeSql function
--
Key: SOLR-2141
URL: https://issues.apache.org/jira/browse/SOLR-2141
Project: Solr
Issue Type: Bug
Components: contrib - DataImportHandler
Affects Versions: 1.4.1
Environment: openjdk 1.6.0 b12
Reporter: Edward Rudd
Assignee: Koji Sekiguchi
Attachments: dih-config.xml, dih-file.xml, SOLR-2141-sample.patch
I have two entities defined, nested in each other..
entity name=article query=select category, subcategory from articles
entity name=other query=select other from othertable where
category='${dataimporter.functions.escapeSql(article.category)}'
AND
subcategory='${dataimporter.functions.escapeSql(article.subcategory)}'
/entity
/entity
Now, when I run that it bombs on any article where subcategory = '' (it's a
NOT NULL column so empty string is there) If i do where subcategory!='' in
the article query it works fine (aside from not pulling in all of the
articles).
org.apache.solr.handler.dataimport.DataImportHandlerException:
java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:424)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:383)
at
org.apache.solr.handler.dataimport.DocBuilder.doFullDump(DocBuilder.java:242)
at
org.apache.solr.handler.dataimport.DocBuilder.execute(DocBuilder.java:180)
at
org.apache.solr.handler.dataimport.DataImporter.doFullImport(DataImporter.java:331)
at
org.apache.solr.handler.dataimport.DataImporter.runCmd(DataImporter.java:389)
at
org.apache.solr.handler.dataimport.DataImporter$1.run(DataImporter.java:370)
Caused by: java.lang.NullPointerException
at
org.apache.solr.handler.dataimport.EvaluatorBag$1.evaluate(EvaluatorBag.java:75)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:216)
at
org.apache.solr.handler.dataimport.EvaluatorBag$5.get(EvaluatorBag.java:204)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.resolve(VariableResolverImpl.java:107)
at
org.apache.solr.handler.dataimport.TemplateString.fillTokens(TemplateString.java:81)
at
org.apache.solr.handler.dataimport.TemplateString.replaceTokens(TemplateString.java:75)
at
org.apache.solr.handler.dataimport.VariableResolverImpl.replaceTokens(VariableResolverImpl.java:87)
at
org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(SqlEntityProcessor.java:71)
at
org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(EntityProcessorWrapper.java:237)
at
org.apache.solr.handler.dataimport.DocBuilder.buildDocument(DocBuilder.java:357)
... 6 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
