I created a ticket for this too - connectors-261.
Afaik, documentum dfc remains under a proprietary license and may not be
redistributed. i don't know about livelink lapi but if you have a link please
share it.
Karl
-Original Message-
From: ext Alex Ott
Sent: 21/09/2011, 6:30 AM
I've already raised the nightly build issue repeatedly. I don't have the
resources or knowledge to set one up myself. Simon volunteered at one point,
but then got busy. Grant said it was unnecessary.
Karl
From: ext Jack Krupansky
In any open-source project there is expected to be some differences in
individual coding styles. There is often also incomplete understanding of the
reasoning behind the multitude of architectural decisions made during
development, or the history of the project. It is thus important to be
The sources were downloaded from www.json.org, and are licensed accordingly.
There is no build available from www.json.org. If you know of a prebuilt
version of these sources, by all means point us at it.
Mavenization is a different issue, and will have to be done independently.
Karl
+1 from me.
Karl
-Original Message-
From: ext Robert Muir [mailto:rcm...@gmail.com]
Sent: Monday, August 23, 2010 4:05 PM
To: connectors-dev@incubator.apache.org
Subject: change the format of CHANGES.txt
Hello,
I wanted to suggest that we slightly alter the format of CHANGES.txt.
Most
I think that providing tools/help for implementing the UI pieces of connectors
is a perfectly reasonable thing to do. However, I strongly believe that the UI
components should remain described as part of the connector interfaces.
Breaking their implementations out within individual connectors
Connector contributions are always welcome, even if others are not using it as
of yet. Can you create a ticket which describes the connector and its
environment (including the security model the repository uses, and what
authority connector is appropriate to use with it), and attach your
Grant, what are the next steps here?
Karl
-Original Message-
From: Wright Karl (Nokia-MS/Cambridge)
Sent: Friday, August 13, 2010 5:53 PM
To: connectors-dev@incubator.apache.org
Subject: RE: Project status and name
I don't think the name change is tied at all to the incubation status.
Folks,
Lucene Connectors Framework is currently an incubating subproject of Lucene.
The PMC has indicated that it's not thrilled with the idea of LCF being a
subproject, and that its status should change at some point in the future.
Note that this status change would be theoretically
I've updated the comment to be consistent with the code.
I am sorry that the documentation in the wiki seems complex. I've tried to
cover both the basics and the important details, which means it is more
in-depth than hello world. Unfortunately, the details are essential in
getting a
That's great news!
If you could, can you create a JIRA ticket through
https://issues.apache.org/jira , and when you have a connector ready, attach an
svn diff as a .patch file to that ticket. We'll then review it, and
incorporate it as part of the LCF build.
Thanks,
Karl
-Original
Let me get this straight. There is a way you can deploy LCF that does
everything you are currently asking for. But you are not willing to use it.
Why?
Karl
-Original Message-
From: ext Jack Krupansky (JIRA) [mailto:j...@apache.org]
Sent: Tuesday, July 13, 2010 4:48 PM
To:
So all you want to see is a postgresql version of QuickStart? That's actually
trivial - it's a one-line modification to the properties.xml file. My
suggestion is to simply address this with documentation.
That would help. Keep in mind the Jira issue for bundling the database
server as well.
I have neither the time nor the inclination to tackle the postgresql bundling
proposal. You are on your own there. If you believe that LCF 1.0 cannot be
released without such a canned installation
Hi Erik,
The reason the fields are broken out is because, in metacarta's experience,
some users are not that bright or technical, and it's better to lead them
through the process of constructing a proper url than to ask them to just type
one. Also, the javascript checking helps.
I have no
I think having a radio button in this situation would complicate the UI. I'd
like to avoid doing that if the benefit is marginal.
Constructing a Solr URL requires knowledge of precisely how to do that.
Questions like, what server? What port? What core? What protocol? are more
basic.
Thanks - I fought with wiki.apache.org a while this morning, reset my password
again, and now I have access too. So next month I should be able to plop it in
there again.
Karl
-Original Message-
From: Grant Ingersoll [mailto:gsi...@gmail.com] On Behalf Of ext Grant Ingersoll
Sent:
Hi all (and especially Eric),
I began work on CONNECTORS-40 in the agreed-upon branch. So far, I've checked
in the modifications needed to pull output connector UI out of JSP, and also
did the conversion of the gts output connector from JSP. This looks reasonably
good to me, other than the
This is basic java 101.
The command-line argument java.io.tmpdir is a command-line switch that you can
use to put java's temporary file directory anywhere you like. The java
defaults on Windows for this parameter are usually just fine. So if you have a
special setup, you will need to modify
That means that the directory pointed at by java.io.temp is not writable, and a
temporary file cannot be created. You must correct this before anything
involving blobs will work.
Karl
--- original message ---
From: ext rohan.gpa...@cognizant.com rohan.gpa...@cognizant.com
Subject: Cannot
Open jdk does not seem to work properly with most java applications at this
time, although it has continued to improve. Its switch incompatibilities stop
it from working with ant at this time, so one cannot even build LCF with it.
Karl
From: ext
This actually did work, oddly enough. I wonder how Derby is undoing the
read-only attribute on those directories? But in any case, I'm revamping the
core setup/shutdown code again so that there's a decent hook in place to do the
derby shutdown.
Karl
-Original Message-
From: ext
I've been trying to get some basic tests working under Junit. Unfortunately,
I've run into a Derby problem which prevents these tests from working.
What happens is this. Derby, when it creates a database, forces a number of
directories within the database to read-only. Unfortunately, unless
Huh. I wonder how ant is doing it?
Using the ant task directly makes it impossible to do this from within JUnit,
of course, but maybe the same hack can be done inside the test stuff.
Karl
-Original Message-
From: ext Koji Sekiguchi [mailto:k...@r.email.ne.jp]
Sent: Tuesday, June 08,
Yeah, I was pretty surprised too. But on windows it is likely that
File.makeReadOnly() (which is what Derby must be using) doesn't actually do
anything to directories, which would explain the discrepancy.
Karl
-Original Message-
From: ext Mark Miller [mailto:markrmil...@gmail.com]
I just had a look at the sources. Ant's chmod task queries what kind of OS it
is, and if it is the right kind, it actually attempts to fire off the chmod
utility. ;-)
That's pretty hacky. Nice to avoid that if possible.
Now, I was able to get my current set of brain-dead tests to work OK
The reason this occurs is because I am using Derby in embedded mode, and the
restriction appears to be a limitation of that mode of operation. However,
this mode is necessary to meet the testing goal, which was the prime motivator
behind doing a Derby implementation. I am sure that if we were
Yup.
Karl
-Original Message-
From: ext Jack Krupansky [mailto:jack.krupan...@lucidimagination.com]
Sent: Friday, June 04, 2010 12:27 AM
To: connectors-dev@incubator.apache.org
Subject: Re: Derby
Just to be clear, the full sequence would be:
1) Start UI app. Agent process should not be
For what it's worth, after some 5 days of work, and a couple of schema changes
to boot, LCF now runs with Derby.
Some caveats:
(1) You can't run more than one LCF process at a time. That means you need
to either run the daemon or the crawler-ui web application, but you can't run
both at
The daemon does not need to interact with the UI directly, only with the
database. So, you stop the UI, start the daemon, and after a while, shut down
the daemon and restart the UI.
Karl
-Original Message-
From: ext Jack Krupansky [mailto:jack.krupan...@lucidimagination.com]
Sent:
It occurred to me that a classloader plug-in reader for LCF would not achieve
the goal of allowing a fully prebuilt LCF with connector add-ons. The reason,
which should have been obvious from the beginning, is because each connector
consists not only of the Java implementation, but also a UI
A naming convention is what is used now. This is described in the
documentation.
The problem is complicated because a precompiled JSP class will not fly - the
package name is going to be different from application server to application
server. So, either:
- we abandon the thought of
The observation about JSPs is exactly what I was alluding to.
Does the entire UI have to be converted to Velocity for this approach to work?
There's an intermediate path that would involve converting only the connector
portions, which might be viable.
Karl
-Original Message-
From:
I've just spelunked through what I could find online, and it seems at least
plausible to use Velocity for various LCF HTML templating needs. The major
concern that I have is that the mix of inline java to HTML in the LCF stuff is
weighted heavily towards inline java - which doesn't seem to be
I've entered a ticket CONNECTORS-40 for this work. What I propose is that this
gets done before first official LCF release, because of the potential
backwards-compatibility issues involved. It is, however, quite a heavy lift -
I can't imagine getting it done in less than a couple of weeks
People who write connectors for LCF before this change occurs will need to
revamp them completely afterwards. That is, unless they contribute them to the
LCF code stream before the work begins...
Second, since there is no Q/A infrastructure yet, there's a very good chance
that stuff will get
The current LCF standard deployment model requires a number of moving parts,
which are probably necessary in some cases, but simply introduce complexity in
others. It has occurred to me that it may be possible to provide an alternate
deployment model involving Jetty, which would reduce the
You forget that building lcf in its entirety requires that you supply
proprietary client components from third-party vendors. So i think it is
unrealistic to expect canned builds that contain everything that you just
deploy. For lcf i think the build cycle will thus be very common.
Getting
I've been fighting with Derby for two days. It's missing a significant amount
of important functionality, and its user and database model are radically
different from all other databases I know of. (I'm also getting nonsense
exceptions from it, but that's another matter.) So regardless of
Dump and restore functionality already exists, but the format is not xml.
Providing and xml dump and restore is straightforward. Making such a file
operate like a true config file is not.
This, by the way, has nothing to do with registering connectors, which is a
datatbase initialization
I already posted a response to this, but since it didn't seem to appear I'm
going to try again.
LCF already has dump and restore commands, but they don't currently write XML,
they write binary data. Providing a way to write and read XML would be
relatively straightforward. But this is *not*
Hi Robert,
The dependency on postgresql is indeed mainly performance, as you say, although
there are a few kinds of queries that I am sure are somewhat
postgresql-specific at this point. These are mainly for the reporting
features, though. So your idea could work in a limited way.
Obviously
There is an abstraction layer, and it is pretty solid, but (as you know),
database abstraction subtleties are pretty significant. The way a database
gathers statistics, for example, will determine how often you can get away with
doing an ANALYZE, and the sensitivity of the database's planner
I agree with this, but I think for unit tests, its best to have a very
simple new clean world for each test.
I think testing the postgres integration is not really unit tests at
all but something else, and we could make it a separate test module.
I have no problem with supporting both some
I found this message in an email thread from forrest-dev:
Hi!
I had trouble with the PDF output as well (in Forrest 0.8) when I tried
to use images scanned from A4 paper in full size. I had to reduce the
resolution of the images down to approx. 840 x 1140 pixels in order to
have them included in
A personal build of forrest-0.9 works properly, although there's a bunch of
traces and warnings that appear at various points. I'm happy with the results
though, so I will update the wiki page to mention that website development
requires 0.9 or better.
Karl
-Original Message-
From:
Please let me know what you think.
= Lucene Connectors Framework =
=== Description ===
Lucene Connectors Framework is an incremental crawler framework and set of
connectors designed to pull documents from various kinds of repositories into
search engine indexes or other targets. The current
Hi all,
I just noticed that the PDFs that Forrest produces do not have any of the
images in them that the online documentation has, so I was wondering you might
know what I was doing wrong.
The source code looks something like this for each image:
br/br/
figure
With regards schema extension, I believe we need to be very careful here, as
requiring index-time storage of access control data will pose a problem for any
use cases where the access control needs to change (maybe often, maybe only
occasionally). I'm trying to think of a use case where this
Hi Solr-knowledgeable folks,
The LCF Solr SearchComponent plugin I'm developing doesn't quite work. The
query I'm trying to do is:
-(allow_token_document:*) and -(deny_token_document:*) and the user's search
The result I'm seeing is that everything in the user's search matches, unlike
what I
Turns out that, for the standard requestHandler, running this SearchComponent
first causes its rewritten query to be lost. Running last fixed the problem.
(I'd *love* to know why that would be necessary.)
But I'd still like comment as to whether the WildcardFilter construct is
expected to be
Adding to the getFilters() list seems reasonable - although, to be fair, my
code does seem to work as intended when the component is added last. I'll do
some experimentation and see what model things work most consistently with.
TermRangeQuery doesn't seem to map readily to the functionality
Turns out that FilteredQuery is what is causing the issue in this case. I
removed FilteredQuery, and instead constructed the search using Query objects
instead of Filter objects, and everything is happy now.
Karl
From: Wright Karl (Nokia-S/Cambridge)
Ok, not hearing back from Peter, I've done some Solr research and written some
code that might work. The approach I've taken is most similar to SOLR 1834,
other than the LCF-centric logic. Hopefully there will be a chance to try this
out in a full end-to-end way on the weekend, after which I
Looking around for no-Apache java-only solutions to the AD authentication
problem, it seems to me that what we mainly have available is JAAS plus the
following JAAS login module:
com.sun.security.auth.module.Krb5LoginModule
... which should permit AD authentication to take place, if properly
Hi Peter,
I've attached a diagram that is not in the wiki as of yet, and I'll try to
answer your questions.
Are the ACCESS_TOKEN and DENY_TOKEN values whatever have been stored for a
particular user in the underlying acl store (e.g. Active Directory)?
How does AD and/or LCF handle storing
Hi Peter,
* What happens if/when you want to add explicit user access to some [group
of] documents ? (i.e. not via a group)
In LCF, you change the permissions on the appropriate resource, and then you
run your LCF job again to update those permissions. Since LCF is an
incremental
Hi Grant,
I've done a fair bit of work on the end-user documentation, but it isn't
regularly pushing out to the site. Can you kick it (or whatever it was you did
last time)? They still haven't granted me incubator group membership, so I'm
stuck.
Karl
58 matches
Mail list logo
