[jira] Updated: (SOLR-1203) We should add an example of setting the update.processor for a given RequestHandler
[ https://issues.apache.org/jira/browse/SOLR-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-1203: -- Description: a commented out example that points to the commented out example update chain or just as good: a comment above the current update chain example explaining how to attach it to a handler. (was: a commented out example that points to the commented out example update chain) > We should add an example of setting the update.processor for a given > RequestHandler > --- > > Key: SOLR-1203 > URL: https://issues.apache.org/jira/browse/SOLR-1203 > Project: Solr > Issue Type: Improvement >Reporter: Mark Miller >Assignee: Mark Miller >Priority: Minor > Fix For: 1.4 > > > a commented out example that points to the commented out example update chain > or just as good: a comment above the current update chain example explaining > how to attach it to a handler. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1203) We should add an example of setting the update.processor for a given RequestHandler
[ https://issues.apache.org/jira/browse/SOLR-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746561#action_12746561 ] Mark Miller commented on SOLR-1203: --- I'm not looking for every possible example. But since we give an example of a custom update chain, it seems we might give an example or pointer on how to actually put it in use? Its kind of a frustrating example otherwise. It should be in the Wiki as well. > We should add an example of setting the update.processor for a given > RequestHandler > --- > > Key: SOLR-1203 > URL: https://issues.apache.org/jira/browse/SOLR-1203 > Project: Solr > Issue Type: Improvement >Reporter: Mark Miller >Assignee: Mark Miller >Priority: Minor > Fix For: 1.4 > > > a commented out example that points to the commented out example update chain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1203) We should add an example of setting the update.processor for a given RequestHandler
[ https://issues.apache.org/jira/browse/SOLR-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746547#action_12746547 ] Lance Norskog commented on SOLR-1203: - I am all for examples, but the example schema.xml and solrconfig.xml cannot contain examples for every possible use of the tools. Maybe this could go in the wiki instead? > We should add an example of setting the update.processor for a given > RequestHandler > --- > > Key: SOLR-1203 > URL: https://issues.apache.org/jira/browse/SOLR-1203 > Project: Solr > Issue Type: Improvement >Reporter: Mark Miller >Assignee: Mark Miller >Priority: Minor > Fix For: 1.4 > > > a commented out example that points to the commented out example update chain -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1229) deletedPkQuery feature does not work when pk and uniqueKey field do not have the same value
[
https://issues.apache.org/jira/browse/SOLR-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746546#action_12746546
]
Lance Norskog commented on SOLR-1229:
-
Noble, what is this broken functionality?
I just did a full update and all unit tests work. If you describe the problem I
will do the unit test and fix it.
> deletedPkQuery feature does not work when pk and uniqueKey field do not have
> the same value
> ---
>
> Key: SOLR-1229
> URL: https://issues.apache.org/jira/browse/SOLR-1229
> Project: Solr
> Issue Type: Bug
> Components: contrib - DataImportHandler
>Affects Versions: 1.4
>Reporter: Erik Hatcher
>Assignee: Erik Hatcher
> Fix For: 1.4
>
> Attachments: SOLR-1229.patch, SOLR-1229.patch, SOLR-1229.patch,
> SOLR-1229.patch, SOLR-1229.patch, SOLR-1229.patch, tests.patch
>
>
> Problem doing a delta-import such that records marked as "deleted" in the
> database are removed from Solr using deletedPkQuery.
> Here's a config I'm using against a mocked test database:
> {code:xml}
>
>
>
>pk="board_id"
>transformer="TemplateTransformer"
>deletedPkQuery="select board_id from boards where deleted = 'Y'"
>query="select * from boards where deleted = 'N'"
>deltaImportQuery="select * from boards where deleted = 'N'"
>deltaQuery="select * from boards where deleted = 'N'"
>preImportDeleteQuery="datasource:board">
>
>
>
>
>
>
> {code}
> Note that the uniqueKey in Solr is the "id" field. And its value is a
> template board-.
> I noticed the javadoc comments in DocBuilder#collectDelta it says "Note: In
> our definition, unique key of Solr document is the primary key of the top
> level entity". This of course isn't really an appropriate assumption.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1045) Build Solr index using Hadoop MapReduce
[
https://issues.apache.org/jira/browse/SOLR-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746545#action_12746545
]
Alex Baranov commented on SOLR-1045:
{quote}write a Solr index in a ram directory{quote}
Please, take a look at [https://issues.apache.org/jira/browse/SOLR-1379] -
RAMDirectoryFactory
> Build Solr index using Hadoop MapReduce
> ---
>
> Key: SOLR-1045
> URL: https://issues.apache.org/jira/browse/SOLR-1045
> Project: Solr
> Issue Type: New Feature
>Reporter: Ning Li
> Attachments: SOLR-1045.0.patch
>
>
> The goal is a contrib module that builds Solr index using Hadoop MapReduce.
> It is different from the Solr support in Nutch. The Solr support in Nutch
> sends a document to a Solr server in a reduce task. Here, the goal is to
> build/update Solr index within map/reduce tasks. Also, it achieves better
> parallelism when the number of map tasks is greater than the number of reduce
> tasks, which is usually the case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1379) Add RAMDirectoryFactory
[
https://issues.apache.org/jira/browse/SOLR-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Baranov updated SOLR-1379:
---
Attachment: SOLR-1379.patch
Attached new patch. It eliminates the previously mentioned constraint.
I managed not to change the existing classes, just new ones were added. But I
think that we should look closer at using DirectoryFactory for accessing the
Directory instance for the index. I believe re-opening Directory is overused in
the current code. It didn't cause any problem because before introducing
RAMDirectoryFactory only filesystem-based directories were used, but still it
may affect the performance and lead to unwanted defects similar to the
mentioned in the previous comment.
> Add RAMDirectoryFactory
> ---
>
> Key: SOLR-1379
> URL: https://issues.apache.org/jira/browse/SOLR-1379
> Project: Solr
> Issue Type: New Feature
>Affects Versions: 1.3
>Reporter: Alex Baranov
>Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1379.patch, SOLR-1379.patch
>
>
> Implement class RAMDirectoryFactory to make possible using RAMDirectory by
> adding the next configuration in solrconfig.xml:
> {code} class="org.apache.solr.core.RAMDirectoryFactory"/>{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1163) Solr Explorer - A generic GWT client for Solr
[
https://issues.apache.org/jira/browse/SOLR-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746528#action_12746528
]
Lance Norskog commented on SOLR-1163:
-
Voted! I'm an American, so no democracy jokes, please.
About licensing - does Google put any license restrictions on distributed code?
> Solr Explorer - A generic GWT client for Solr
> -
>
> Key: SOLR-1163
> URL: https://issues.apache.org/jira/browse/SOLR-1163
> Project: Solr
> Issue Type: New Feature
> Components: web gui
>Affects Versions: 1.3
>Reporter: Uri Boness
> Attachments: graphics.zip, solr-explorer.patch, solr-explorer.patch
>
>
> The attached patch is a GWT generic client for solr. It is currently
> standalone, meaning that once built, one can open the generated HTML file in
> a browser and communicate with any deployed solr. It is configured with it's
> own configuration file, where one can configure the solr instance/core to
> connect to. Since it's currently standalone and completely client side based,
> it uses JSON with padding (cross-side scripting) to connect to remote solr
> servers. Some of the supported features:
> - Simple query search
> - Sorting - one can dynamically define new sort criterias
> - Search results are rendered very much like Google search results are
> rendered. It is also possible to view all stored field values for every hit.
> - Custom hit rendering - It is possible to show thumbnails (images) per hit
> and also customize a view for a hit based on html templates
> - Faceting - one can dynamically define field and query facets via the UI. it
> is also possible to pre-configure these facets in the configuration file.
> - Highlighting - you can dynamically configure highlighting. it can also be
> pre-configured in the configuration file
> - Spellchecking - you can dynamically configure spell checking. Can also be
> done in the configuration file. Supports collation. It is also possible to
> send "build" and "reload" commands.
> - Data import handler - if used, it is possible to send a "full-import" and
> "status" command ("delta-import" is not implemented yet, but it's easy to add)
> - Console - For development time, there's a small console which can help to
> better understand what's going on behind the scenes. One can use it to:
> ** view the client logs
> ** browse the solr scheme
> ** View a break down of the current search context
> ** View a break down of the query URL that is sent to solr
> ** View the raw JSON response returning from Solr
> This client is actually a platform that can be greatly extended for more
> things. The goal is to have a client where the explorer part is just one view
> of it. Other future views include: Monitoring, Administration, Query Builder,
> DataImportHandler configuration, and more...
> To get a better view of what's currently possible. We've set up a public
> version of this client at: http://search.jteam.nl/explorer. This client is
> configured with one solr instance where crawled YouTube movies where indexed.
> You can also check out a screencast for this deployed client:
> http://search.jteam.nl/help
> The patch created a new folder in the contrib. directory. Since the patch
> doesn't contain binaries, an additional zip file is provides that needs to be
> extract to add all the required graphics. This module is maven2 based and is
> configured in such a way that all GWT related tools/libraries are
> automatically downloaded when the modules is compiled. One of the artifacts
> of the build is a war file which can be deployed in any servlet container.
> NOTE: this client works best on WebKit based browsers (for performance
> reason) but also works on firefox and ie 7+. That said, it should be taken
> into account that it is still under development.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
multivalued integer testing
Hello, I'm trying to write a test using a multivalued integer, for the StatsComponents. I've defined a field with multivalued="true" and was able to successfully add a document with multiple integer values. However, when testing if the fieldtype is multivalued: ft.isMultiValued() the testing environment returns false, which screws up the component I'm trying to test. The component works fine in a production environment - I'm wondering what I'm doing wrong here? Thanks, -Harish -- View this message in context: http://www.nabble.com/multivalued-integer-testing-tp25097576p25097576.html Sent from the Solr - Dev mailing list archive at Nabble.com.
[jira] Commented: (SOLR-1379) Add RAMDirectoryFactory
[
https://issues.apache.org/jira/browse/SOLR-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746508#action_12746508
]
Alex Baranov commented on SOLR-1379:
Moreover, with the RAMDirectoryFactory provided by this patch updating
documents via Solr doesn't work properly.
Example of the scenario in which this RAMDirectoryFactory is usable is when
persistent (on file system) index is created/updated by another application
(perhaps using pure luce approach to maintain this) and Solr core is reloaded
whenever updates should affect the search. One of the possible reasons to use
this scenario is to speed up search with RAMDirectory when index changes rarely
on doesn't change at all.
> Add RAMDirectoryFactory
> ---
>
> Key: SOLR-1379
> URL: https://issues.apache.org/jira/browse/SOLR-1379
> Project: Solr
> Issue Type: New Feature
>Affects Versions: 1.3
>Reporter: Alex Baranov
>Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1379.patch
>
>
> Implement class RAMDirectoryFactory to make possible using RAMDirectory by
> adding the next configuration in solrconfig.xml:
> {code} class="org.apache.solr.core.RAMDirectoryFactory"/>{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-1379) Add RAMDirectoryFactory
[
https://issues.apache.org/jira/browse/SOLR-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Baranov updated SOLR-1379:
---
Attachment: SOLR-1379.patch
Attached patch with the implemented class.
However, the next constraint is present: RAMDirectoryFactory can be used only
when the index already present on disk. For example, first, we can start Solr
using StandardDirectoryFactory (default) so that Solr creates needed files in
dataDir.
If this constraint is quite normal, please, let me know. To avoid it some
changes need to be done in SolrCore and in DirectoryFactory API.
Anyway I'm going to provide an alternative patch later to eliminate the
constraint.
> Add RAMDirectoryFactory
> ---
>
> Key: SOLR-1379
> URL: https://issues.apache.org/jira/browse/SOLR-1379
> Project: Solr
> Issue Type: New Feature
>Affects Versions: 1.3
>Reporter: Alex Baranov
>Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1379.patch
>
>
> Implement class RAMDirectoryFactory to make possible using RAMDirectory by
> adding the next configuration in solrconfig.xml:
> {code} class="org.apache.solr.core.RAMDirectoryFactory"/>{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SOLR-1379) Add RAMDirectoryFactory
Add RAMDirectoryFactory
---
Key: SOLR-1379
URL: https://issues.apache.org/jira/browse/SOLR-1379
Project: Solr
Issue Type: New Feature
Affects Versions: 1.3
Reporter: Alex Baranov
Priority: Minor
Fix For: 1.4
Implement class RAMDirectoryFactory to make possible using RAMDirectory by
adding the next configuration in solrconfig.xml:
{code}{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
updated solrjs wiki page
hey all, as solrjs was now successfully moved to client/javascript, I updated the wiki page at http://wiki.apache.org/solr/SolrJS to make it easy for the user to quickstart. Only a few steps are needed to see and explore the example locally. Feedback appreciated concerning contents, spelling etc.. I may create a small patch soon to add some README that points to the wiki and cleans up unused file in the example tree. As I got a bunch of off-list questions while I was on vacation, I'll create a status summary mail for users list tomorrow pointing out the wiki page and current issues (eg. ie7) and thoughts. regards, matthias
Hudson build is back to normal: Solr-trunk #902
See http://hudson.zones.apache.org/hudson/job/Solr-trunk/902/changes
