date:20141018

Re: Fwd: Pylucene jvm CharArraySet Error

2014-10-18 Thread Andi Vajda



On Sat, 18 Oct 2014, Alexander Alex wrote:


The init file in the pylucene egg. Below is it:


import os, sys

if sys.platform == 'win32':
 from jcc.windows import add_jvm_dll_directory_to_path
 add_jvm_dll_directory_to_path()
 import jcc, _lucene
else:
 import _lucene

__dir__ = os.path.abspath(os.path.dirname(__file__))

class JavaError(Exception):
 def getJavaException(self):
   return self.args[0]
 def __str__(self):
   writer = StringWriter()
   self.getJavaException().printStackTrace(PrintWriter(writer))
   return \n.join((super(JavaError, self).__str__(), Java
stacktrace:, str(writer)))

class InvalidArgsError(Exception):
 pass

_lucene._set_exception_types(JavaError, InvalidArgsError)

VERSION = 3.6.2
CLASSPATH = [os.path.join(__dir__, lucene-core-3.6.2.jar),
os.path.join(__dir__, lucene-analyzers-3.6.2.jar), os.path.join(__dir__,
lucene-memory-3.6.2.jar), os.path.join(__dir__,
lucene-highlighter-3.6.2.jar), os.path.join(__dir__, extensions.jar),
os.path.join(__dir__, lucene-queries-3.6.2.jar), os.path.join(__dir__,
lucene-grouping-3.6.2.jar), os.path.join(__dir__,
lucene-join-3.6.2.jar), os.path.join(__dir__, lucene-facet-3.6.2.jar),
os.path.join(__dir__, lucene-spellchecker-3.6.2.jar)]
CLASSPATH = os.pathsep.join(CLASSPATH)
_lucene.CLASSPATH = CLASSPATH
_lucene._set_function_self(_lucene.initVM, _lucene)

from _lucene import *


Thanks. This looks like the vanilla __init__.py file in the pylucene egg.
I see no modifications from you for, I quote path of the dependencies to 
classpath in the init.py file.


To be sure there is no misunderstanding here, this is what I understand from 
you so far:

  - you downloaded, built and installed PyLucene 3.6.2
(with what Python version and what Java version ?)
  - you then compiled a new class and added it to two JAR files,
lucene-core-3.6.2.jar and lucene-analyzers-3.6.2.jar
(with that Java version ?, why did you modify two JAR files ?
 why not create your own JAR file with your extra stuff ?)
  - you then edited __init__.py to reflect this change but I don't see
any change in the file you pasted nor why the change is needed if you
just modified existing JAR files (in the right location, inside the
PyLucene egg, right ?)
  - you did not rebuild PyLucene itself after making any of these changes

If this mental picture is correct then this is not the right way to go about 
it. The proper way to modify Lucene Core and then PyLucene is to:

  - compile and build your new classes using the same version of Java (and
Lucene)
  - create a new JAR file containing your extra stuff
  - test that it all works with a simple Java program that uses Lucene core
and your new code together
  - _then_ rebuild PyLucene including your new JAR file either by:
 - adding it to the list of JAR files being wrapped by JCC via --jar
   in the PyLucene Makefile
 - OR pass it to JCC via --include instead so that it just becomes part
   of the new PyLucene egg (ensuring it being inside the egg and on the
   classpath but no Python wrappers for it are generated)

To get command line argument help from JCC run python -m jcc --help (or 
whatever the correct invocation is for your version of Python).


Andi..


On Sat, Oct 18, 2014 at 12:29 AM, Andi Vajda va...@apache.org wrote:



On Sat, 18 Oct 2014, Alexander Alex wrote:

 ok. I built the class files for the java files attached herein, add them

to
lucene-core-3.6.2.jar at org.apache.lucene.analysis and
lucene-analyzers-3.6.2.jar at org.apache.lucene.analysis. I then added the
path of the dependencies to classpath in the init.py file.



What init.py file ?
Can you paste the contents of that file here, please ?

Andi..


 I ran the

typical index file using this customized analyzer through PythonAnalyzer
and got the above error. Meanwhile, I had earlier ran the index file using
standard analyzer before adding the classes and it worked. After running
the index file with the customized analyzer failed, I tried again with the
standard analyzer which had earlier worked before adding the classes but
failed this time around with same error message as above. I guess the
problem has to do with array compatibility in java and python but I don't
really know. Thanks.



On Fri, Oct 17, 2014 at 7:23 PM, Andi Vajda va...@apache.org wrote:



On Fri, 17 Oct 2014, Alexander Alex wrote:

 Meanwhile, am using lucene 3.6.2 version. The problem is jvm
instantiation


from any python code using lucene caused as a result of the classes I
added
to lucene core.

-- Forwarded message --

I added a customized lucene analyzer class to lucene core in Pylucene.



Please explain in _detail_ the steps you followed to accomplish this.
A log of all the commands you ran would be ideal.

Thanks !

Andi..


 This class is google guava as a dependency because of the array handling


function available in com.google.common.collect.Iterables in guava.
When
I tried to index using this analyzer, I

Re: Fwd: Pylucene jvm CharArraySet Error

2014-10-18 Thread Alexander Alex

Thanks Andi. am going to try these suggestions out.

On Sat, Oct 18, 2014 at 9:55 PM, Andi Vajda va...@apache.org wrote:


 On Sat, 18 Oct 2014, Alexander Alex wrote:

  The init file in the pylucene egg. Below is it:


 import os, sys

 if sys.platform == 'win32':
  from jcc.windows import add_jvm_dll_directory_to_path
  add_jvm_dll_directory_to_path()
  import jcc, _lucene
 else:
  import _lucene

 __dir__ = os.path.abspath(os.path.dirname(__file__))

 class JavaError(Exception):
  def getJavaException(self):
return self.args[0]
  def __str__(self):
writer = StringWriter()
self.getJavaException().printStackTrace(PrintWriter(writer))
return \n.join((super(JavaError, self).__str__(), Java
 stacktrace:, str(writer)))

 class InvalidArgsError(Exception):
  pass

 _lucene._set_exception_types(JavaError, InvalidArgsError)

 VERSION = 3.6.2
 CLASSPATH = [os.path.join(__dir__, lucene-core-3.6.2.jar),
 os.path.join(__dir__, lucene-analyzers-3.6.2.jar), os.path.join(__dir__,
 lucene-memory-3.6.2.jar), os.path.join(__dir__,
 lucene-highlighter-3.6.2.jar), os.path.join(__dir__, extensions.jar),
 os.path.join(__dir__, lucene-queries-3.6.2.jar), os.path.join(__dir__,
 lucene-grouping-3.6.2.jar), os.path.join(__dir__,
 lucene-join-3.6.2.jar), os.path.join(__dir__, lucene-facet-3.6.2.jar),
 os.path.join(__dir__, lucene-spellchecker-3.6.2.jar)]
 CLASSPATH = os.pathsep.join(CLASSPATH)
 _lucene.CLASSPATH = CLASSPATH
 _lucene._set_function_self(_lucene.initVM, _lucene)

 from _lucene import *


 Thanks. This looks like the vanilla __init__.py file in the pylucene egg.
 I see no modifications from you for, I quote path of the dependencies to
 classpath in the init.py file.

 To be sure there is no misunderstanding here, this is what I understand
 from you so far:
   - you downloaded, built and installed PyLucene 3.6.2
 (with what Python version and what Java version ?)
   - you then compiled a new class and added it to two JAR files,
 lucene-core-3.6.2.jar and lucene-analyzers-3.6.2.jar
 (with that Java version ?, why did you modify two JAR files ?
  why not create your own JAR file with your extra stuff ?)
   - you then edited __init__.py to reflect this change but I don't see
 any change in the file you pasted nor why the change is needed if you
 just modified existing JAR files (in the right location, inside the
 PyLucene egg, right ?)
   - you did not rebuild PyLucene itself after making any of these changes

 If this mental picture is correct then this is not the right way to go
 about it. The proper way to modify Lucene Core and then PyLucene is to:
   - compile and build your new classes using the same version of Java (and
 Lucene)
   - create a new JAR file containing your extra stuff
   - test that it all works with a simple Java program that uses Lucene core
 and your new code together
   - _then_ rebuild PyLucene including your new JAR file either by:
  - adding it to the list of JAR files being wrapped by JCC via --jar
in the PyLucene Makefile
  - OR pass it to JCC via --include instead so that it just becomes part
of the new PyLucene egg (ensuring it being inside the egg and on the
classpath but no Python wrappers for it are generated)

 To get command line argument help from JCC run python -m jcc --help (or
 whatever the correct invocation is for your version of Python).

 Andi..


  On Sat, Oct 18, 2014 at 12:29 AM, Andi Vajda va...@apache.org wrote:


 On Sat, 18 Oct 2014, Alexander Alex wrote:

  ok. I built the class files for the java files attached herein, add them

 to
 lucene-core-3.6.2.jar at org.apache.lucene.analysis and
 lucene-analyzers-3.6.2.jar at org.apache.lucene.analysis. I then added
 the
 path of the dependencies to classpath in the init.py file.


 What init.py file ?
 Can you paste the contents of that file here, please ?

 Andi..


  I ran the

 typical index file using this customized analyzer through PythonAnalyzer
 and got the above error. Meanwhile, I had earlier ran the index file
 using
 standard analyzer before adding the classes and it worked. After running
 the index file with the customized analyzer failed, I tried again with
 the
 standard analyzer which had earlier worked before adding the classes but
 failed this time around with same error message as above. I guess the
 problem has to do with array compatibility in java and python but I
 don't
 really know. Thanks.



 On Fri, Oct 17, 2014 at 7:23 PM, Andi Vajda va...@apache.org wrote:


  On Fri, 17 Oct 2014, Alexander Alex wrote:

  Meanwhile, am using lucene 3.6.2 version. The problem is jvm
 instantiation

  from any python code using lucene caused as a result of the classes I
 added
 to lucene core.

 -- Forwarded message --

 I added a customized lucene analyzer class to lucene core in Pylucene.


  Please explain in _detail_ the steps you followed to accomplish this.
 A log of all the commands you ran would be

[jira] [Commented] (SOLR-6474) Smoke tester should use the Solr start scripts to start Solr

2014-10-18 Thread Anurag Sharma (JIRA)


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

Anurag Sharma commented on SOLR-6474:
-

This is lucene smoke test or solr? 
Other the smoke tester, how about updating all the references of starting solr 
java -jar start.jar with start script  in SOLR-3617?

 Smoke tester should use the Solr start scripts to start Solr
 

 Key: SOLR-6474
 URL: https://issues.apache.org/jira/browse/SOLR-6474
 Project: Solr
  Issue Type: Task
  Components: scripts and tools
Reporter: Shalin Shekhar Mangar
  Labels: difficulty-easy, impact-low
 Fix For: 5.0


 We should use the Solr bin scripts created by SOLR-3617 in the smoke tester 
 to test Solr.



--
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] (LUCENE-6007) Failed attempt of downloading javax:activation javadoc

2014-10-18 Thread Ilia Sretenskii (JIRA)


[ 
https://issues.apache.org/jira/browse/LUCENE-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175885#comment-14175885
 ] 

Ilia Sretenskii commented on LUCENE-6007:
-

Unfortunately I can not help you with that, guys.
My experience is limited with [Apache Maven|http://maven.apache.org/] and I 
honestly have no idea about how [Apache Ant|http://ant.apache.org/] and [Apache 
Ivy|http://ant.apache.org/ivy/] work at all.
Isn't that just too many of different dependency managers to mess with, that 
are causing their own conflicts troubles?

 Failed attempt of downloading javax:activation javadoc
 --

 Key: LUCENE-6007
 URL: https://issues.apache.org/jira/browse/LUCENE-6007
 Project: Lucene - Core
  Issue Type: Bug
  Components: general/build
Affects Versions: Trunk
 Environment: java version 1.7.0_67
 Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
 Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
 Apache Ant(TM) version 1.9.4 compiled on April 29 2014
 Microsoft Windows Professional 8.1 (6.3.9600) x64
Reporter: Ilia Sretenskii
Assignee: Steve Rowe
  Labels: ant, download, ivy, jar, javadoc, javax, maven
 Attachments: LUCENE-6007.patch


 I have [checked out the trunk source 
 code|https://wiki.apache.org/lucene-java/HowToContribute].
 But then running the following commands fails:
 * [ant clean test|https://wiki.apache.org/lucene-java/HowToContribute]
 * [ant idea|https://wiki.apache.org/lucene-java/HowtoConfigureIntelliJ]
 The failure message says the following:
 {noformat}
 ivy-fail:
 resolve:
 [ivy:retrieve]
 [ivy:retrieve] :: problems summary ::
 [ivy:retrieve]  WARNINGS
 [ivy:retrieve]  [FAILED ] 
 javax.activation#activation;1.1.1!activation.jar(javadoc):  (0ms)
 [ivy:retrieve]   shared: tried
 [ivy:retrieve]
 C:\Users\Ilia\.ivy2\shared\javax.activation\activation\1.1.1\javadocs\activation.jar
 [ivy:retrieve]   public: tried
 [ivy:retrieve]
 http://repo1.maven.org/maven2/javax/activation/activation/1.1.1/activation-1.1.1-javadoc.jar
 [ivy:retrieve]  ::
 [ivy:retrieve]  ::  FAILED DOWNLOADS::
 [ivy:retrieve]  :: ^ see resolution messages for details  ^ ::
 [ivy:retrieve]  ::
 [ivy:retrieve]  :: 
 javax.activation#activation;1.1.1!activation.jar(javadoc)
 [ivy:retrieve]  ::
 [ivy:retrieve]
 [ivy:retrieve]
 [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
 BUILD FAILED
 C:\Users\Ilia\Documents\IdeaProjects\svn.apache.org\lucene\build.xml:61: The 
 following error occurred while executing this line:
 C:\Users\Ilia\Documents\IdeaProjects\svn.apache.org\lucene\extra-targets.xml:39:
  The following error occurred while executing this line:
 C:\Users\Ilia\Documents\IdeaProjects\svn.apache.org\lucene\solr\build.xml:209:
  The following error occurred while executing this line:
 C:\Users\Ilia\Documents\IdeaProjects\svn.apache.org\lucene\solr\common-build.xml:440:
  The following error occurred while executing this line:
 C:\Users\Ilia\Documents\IdeaProjects\svn.apache.org\lucene\solr\common-build.xml:496:
  The following error occurred while executing this line:
 C:\Users\Ilia\Documents\IdeaProjects\svn.apache.org\lucene\solr\contrib\contrib-build.xml:52:
  impossible to resolve dependencies:
 resolve failed - see output for details
 Total time: 53 minutes 19 seconds
 {noformat}
 There was a javadoc file for 
 [javax:activation:1.1-rev-1|http://repo1.maven.org/maven2/javax/activation/activation/1.1-rev-1/],
  but none for 
 [javax:activation:1.1.1|http://repo1.maven.org/maven2/javax/activation/activation/1.1.1/],
  which might be the cause.



--
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-6547) CloudSolrServer query getqtime Exception

2014-10-18 Thread Shawn Heisey (JIRA)

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

Shawn Heisey commented on SOLR-6547:

There's merit either way.

Integer.MAX_VALUE in milliseconds is a little more than 24 days. I doubt you
would ever run into a query that would actually take that long and still have
enough resources to actually finish, so an int has plenty of capacity to handle
QTime. The difference is tiny for a single value, but a long does take up
twice as much memory. If most of the existing code uses an int, I am inclined
to stick with that and change the deviating code.

On the other hand ... everything else related to time in Java *is* represented
as a long, as [~anuragsharma] mentioned. If the value is ever used for
calculation with any of those other numbers, it might save a tiny bit of CPU
time if Java doesn't have to convert.

Switching everything to a long is likely to involve quite a bit of effort to
locate and change every place that it's used, which is a big part of why I
suggest sticking with int. I don't think we would ever *need* a long for
relative times.

CloudSolrServer query getqtime Exception

Key: SOLR-6547
URL: https://issues.apache.org/jira/browse/SOLR-6547
Project: Solr
Issue Type: Bug
Components: SolrJ
Affects Versions: 4.10
Reporter: kevin

We are using CloudSolrServer to query ,but solrj throw Exception ;
java.lang.ClassCastException: java.lang.Long cannot be cast to
java.lang.Integer at
org.apache.solr.client.solrj.response.SolrResponseBase.getQTime(SolrResponseBase.java:76)

48 matches

Mail list logo