[
https://issues.apache.org/jira/browse/SOLR-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-726.
Resolution: Fixed
Committed revision 690131.
Thanks Walter and Noble!
driver and
[
https://issues.apache.org/jira/browse/SOLR-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-728:
---
Fix Version/s: (was: 1.3)
1.4
Unmarking this for 1.3 -- the
I solved this using:
http://www.kfu.com/~nsayer/Java/dyn-jdbc.html
-Grant
On Aug 29, 2008, at 1:04 AM, Shalin Shekhar Mangar (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar
Add support for OmitTf
--
Key: SOLR-739
URL: https://issues.apache.org/jira/browse/SOLR-739
Project: Solr
Issue Type: New Feature
Reporter: Mark Miller
Priority: Minor
Fix For: 1.4
[
https://issues.apache.org/jira/browse/SOLR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-739:
-
Attachment: SOLR-739.patch
Simple patch, but my first look at Schema stuff so merits a bit of scrutiny.
Clearing it out did the trick. Thanks!
On Aug 28, 2008, at 5:54 PM, Chris Hostetter wrote:
: How does Forrest pick them up from siteconf.xml? The reference in
there seems
: to be to a local file and not the one in build/.
catalog.xcat refers to the file using a relative path that goes
[
https://issues.apache.org/jira/browse/SOLR-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher closed SOLR-738.
-
Resolution: Fixed
Please use the solr-user list for usage questions.
Give fact.query a try using range
[
https://issues.apache.org/jira/browse/SOLR-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626993#action_12626993
]
Henri Biestro commented on SOLR-725:
Paul
Would it be fair to say that you fear the
[
https://issues.apache.org/jira/browse/SOLR-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627007#action_12627007
]
Otis Gospodnetic commented on SOLR-731:
---
I've just started looking at
Random nit: in release-candidate/build/docs/who.pdf, Otis's name is spelled
Otis Gospodneti# (final character is a hash mark). - Steve
On 08/29/2008 at 11:16 AM, Grant Ingersoll wrote:
I created a Hudson task to do the building/archival tasks for the
release candidates.It is a on-demand
Are we really sure we want to do this w/o making it configurable on
the QParser? (ala: SOLR-218)
Unless I'm missing something this change breaks back compatibility of for
users who highlight wildcard queries. As i recall: we even have users who
force their prefix queries to be wildcards by
On Fri, Aug 29, 2008 at 12:18 PM, Chris Hostetter
[EMAIL PROTECTED] wrote:
Are we really sure we want to do this w/o making it configurable on
the QParser? (ala: SOLR-218)
I thought about that, but these expanding term queries that have no
bounds are really broken... people who depend on them
: fire. Imagine everything working fine for months, docs being
: occasionally added, until *boom* a magic limit is hit.
:
: I wouldn't be opposed to a config option I guess... but I think the
: default should be something that doesn't unpredictably break (so it
: still wouldn't be 100% back
[
https://issues.apache.org/jira/browse/SOLR-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627035#action_12627035
]
Henri Biestro commented on SOLR-731:
The issue is about having public access from CD to
[
https://issues.apache.org/jira/browse/SOLR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627049#action_12627049
]
Mike Klaas commented on SOLR-739:
-
Haven't looked at the patch, but defaulting to omitTf=true
I've been thinking about the next major version of Solr.
Here's some brainstorming on goals/ideas:
- use a standard IOC container for externalization of configuration
and plugins... Spring springs to mind as the obvious choice here.
May want to use other spring services such as JMX integration,
[
https://issues.apache.org/jira/browse/SOLR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627057#action_12627057
]
Yonik Seeley commented on SOLR-739:
---
I think it's unlikely to matter for non-text fields,
[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-684:
-
Assignee: Hoss Man
Hudson builds do not have the SVN revision because svnversion is not available
[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627059#action_12627059
]
Hoss Man commented on SOLR-684:
---
r690357 should help us solve this problem ... i've made the
On Aug 29, 2008, at 12:05 PM, Steven A Rowe wrote:
Random nit: in release-candidate/build/docs/who.pdf, Otis's name is
spelled Otis Gospodneti# (final character is a hash mark). - Steve
Hmm, that's weird. It's also that way on the current site.
On 08/29/2008 at 11:16 AM, Grant
[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627067#action_12627067
]
Lars Kotthoff commented on SOLR-684:
Hmmm, doesn't look like it :(
[exec] Execute
On Aug 29, 2008, at 2:03 PM, Yonik Seeley wrote:
I've been thinking about the next major version of Solr.
Here's some brainstorming on goals/ideas:
- use a standard IOC container for externalization of configuration
and plugins... Spring springs to mind as the obvious choice here.
May want to
On Aug 29, 2008, at 2:58 PM, Grant Ingersoll wrote:
Onward and upward... Other thoughts ideas?
Better support for Spans, Payloads, Term Vectors. Granted, Spans
just need support via a query parser and the results written to the
output, but Payloads are a bit trickier when it comes to
[
https://issues.apache.org/jira/browse/SOLR-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627071#action_12627071
]
David Smiley commented on SOLR-540:
---
I'd like this incorporated into Solr. I stupidly
checking out 1.3 RC1 i notice that the src Jars and docs Jars
generated for maven (containing the source and and javadocs for each
corrisponding code jar) are included in the dist directory of the
release.
It makes sense to have these for maven users -- but they seem like
overkill for
can someone with a lucene zone account do me a favor and run locate
svnversion on that box for me and reply with the output?
I thought i had a decent solution for SOLR-684, but i forgot that all the
Lucene builds acutally execute on the lucene zone (which aparently doesn't
have the svn
Doesn't seem like maven artifacts should be in the download... that's
what the maven repo is for, right?
-Yonik
On Fri, Aug 29, 2008 at 3:07 PM, Chris Hostetter
[EMAIL PROTECTED] wrote:
checking out 1.3 RC1 i notice that the src Jars and docs Jars generated
for maven (containing the source
Grant, here is what it's supposed to be: Gospodnetić
If Forrest and friends don't like that diacritic, I suppose I can live with
Gospodnetic -- damn i18n! ;)
This is what I see locally:
$ ffxg Gospod
./src/site/src/documentation/content/xdocs/who.xml: liOtis
Gospodneti#263;/li
$ find .
I put it in my path just recently (and that old nightly build runs under my id).
-bash-3.00$ type svnversion
svnversion is /export/home/yonik/bin/svnversion
-bash-3.00$ ls -l /export/home/yonik/bin/svnversion
lrwxrwxrwx 1 yonikother 38 Aug 27 19:18
/export/home/yonik/bin/svnversion
Maybe this is the answer:
http://forrest.apache.org/docs_0_90/faq.html#encoding
And this is what we've got:
$ head -1 src/site/src/documentation/content/xdocs/who.xml
?xml version=1.0?
Sounds like something that would be good to fix in general, but I don't have
forrest set up to try it :(
: If Forrest and friends don't like that diacritic, I suppose I can live
: with Gospodnetic -- damn i18n! ;)
I seem to recall that we had this problem with forrest and the Lucene-Java
who page as well ... over there you are listed in lowly ASCII, without
your I18N goodness.
--
Sematext --
[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627077#action_12627077
]
Hoss Man commented on SOLR-684:
---
yeah ... i forgot the solr hudson builds are actually run on
: Maybe this is the answer:
: http://forrest.apache.org/docs_0_90/faq.html#encoding
my reading of that is that setting an encoding will let you use the
litteral UTF-8 character 9which is what i would expect) but not the end of
the answer...
Another option is to use character entities such
On Aug 29, 2008, at 3:18 PM, Otis Gospodnetic wrote:
Maybe this is the answer:
http://forrest.apache.org/docs_0_90/faq.html#encoding
And this is what we've got:
$ head -1 src/site/src/documentation/content/xdocs/who.xml
?xml version=1.0?
Sounds like something that would be good to fix in
Yeah, no need for them to be in there. I'll take care of it.
On Aug 29, 2008, at 3:07 PM, Chris Hostetter wrote:
checking out 1.3 RC1 i notice that the src Jars and docs Jars
generated for maven (containing the source and and javadocs for each
corrisponding code jar) are included in the
[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627080#action_12627080
]
Lars Kotthoff commented on SOLR-684:
Looks good :)
Hudson builds do not have the SVN
[
https://issues.apache.org/jira/browse/SOLR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627081#action_12627081
]
David Smiley commented on SOLR-334:
---
I intend on submitting a patch very soon which I think
[
https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Harris updated SOLR-284:
--
Attachment: un-hardcode-id.diff
The patch, as currently stands, treats a field called id as a special
[
https://issues.apache.org/jira/browse/SOLR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627084#action_12627084
]
Yonik Seeley commented on SOLR-334:
---
bq. Should I submit a new issue for this or add to
[
https://issues.apache.org/jira/browse/SOLR-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-334.
---
Resolution: Fixed
Fix Version/s: 1.3
resolving this issue.
pluggable query parsers
legacy gettableFiles support not working in 1.3.0-RC1
-
Key: SOLR-740
URL: https://issues.apache.org/jira/browse/SOLR-740
Project: Solr
Issue Type: Bug
Affects Versions: 1.3
[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-684:
--
Fix Version/s: 1.3
I've merged to 1.3 in r690384 and made the appropriate Hudson config changes
for Grant's
[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-684.
---
Resolution: Fixed
Hudson builds do not have the SVN revision because svnversion is not available
On Fri, Aug 29, 2008 at 11:33 PM, Yonik Seeley [EMAIL PROTECTED] wrote:
I've been thinking about the next major version of Solr.
Here's some brainstorming on goals/ideas:
- use a standard IOC container for externalization of configuration
and plugins... Spring springs to mind as the obvious
[
https://issues.apache.org/jira/browse/SOLR-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627108#action_12627108
]
Hoss Man commented on SOLR-684:
---
bq. When you get something like 690356:690357M it's highly
: I haven't gone through with a fine tooth comb yet, hence the prototype in
: the subject line, but my preliminary skimming of it seems like it is on track.
: I will cover it more later today. In the meantime, feedback is appreciated.
I've done some testing with both the Solr 1.2 example and
Add support for rounding dates in DateField
---
Key: SOLR-741
URL: https://issues.apache.org/jira/browse/SOLR-741
Project: Solr
Issue Type: Improvement
Components: search
Affects
Unable to create dynamic fields with custom DataImportHandler transformer
-
Key: SOLR-742
URL: https://issues.apache.org/jira/browse/SOLR-742
Project: Solr
Issue Type:
On 08/29/2008 at 3:24 PM, Chris Hostetter wrote:
I suspect the PDF formatter just doesn't play nicely with the
non-trivial UTF-8 characters.
This is an Apache FOP FAQ; from
http://xmlgraphics.apache.org/fop/faq.html#pdf-characters:
6.2. Some characters are not displayed, or displayed
[
https://issues.apache.org/jira/browse/SOLR-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wojtek Piaseczny updated SOLR-742:
--
Fix Version/s: (was: 1.3)
1.4
Unable to create dynamic fields with
[
https://issues.apache.org/jira/browse/SOLR-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627129#action_12627129
]
Hoss Man commented on SOLR-739:
---
FWIW: this is a situation where reving the schema version
On Fri, Aug 29, 2008 at 2:03 PM, Yonik Seeley [EMAIL PROTECTED] wrote:
- allow more lower level index operations... create a new index at a
given spot, merge multiple indicies, etc.
- possibly add the ability to pull a lucene index from hdfs (via a
plugin if we don't want a hard dependency on
: DataImportHandler should also be considered experimental.
Yonik was specificly refering to response formats/structures, many of
which have had a warning in them cautioning people not to write code that
depends on the exct format (ie: programmaticly parsing th response) until
we decided if
[
https://issues.apache.org/jira/browse/SOLR-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-740:
-
Assignee: Hoss Man
legacy gettableFiles support not working in 1.3.0-RC1
[
https://issues.apache.org/jira/browse/SOLR-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-740.
---
Resolution: Fixed
trunk r690430
1.3 branch r690432
legacy gettableFiles support not working in 1.3.0-RC1
[
https://issues.apache.org/jira/browse/SOLR-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627176#action_12627176
]
Hoss Man commented on SOLR-741:
---
I propose a lot of more general things -- but I'm also a fan
56 matches
Mail list logo
