[
https://issues.apache.org/jira/browse/CONNECTORS-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894259#comment-13894259
]
lalit commented on CONNECTORS-864:
--
I have downloaded from source for 1.4.1 & updated
Ran tests.
+1 from me.
Minoru OSUKA
> On Feb 4, 2014, at 9:33 PM, Karl Wright wrote:
>
> This is a major release of ManifoldCF that includes the following:
>
> - Federated authority support
> - Multiple authorization domains
> - ZooKeeper process coordination
> - Multiple agents processes
> -
[
https://issues.apache.org/jira/browse/CONNECTORS-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894241#comment-13894241
]
Karl Wright commented on CONNECTORS-885:
JobManager.getJobsReadyForStartup() i
Karl Wright created CONNECTORS-885:
--
Summary: Startup sequence also handles ServiceInterruption badly
Key: CONNECTORS-885
URL: https://issues.apache.org/jira/browse/CONNECTORS-885
Project: ManifoldCF
Even if you vote in favor, we'll still need one more vote after that.
Karl
On Thu, Feb 6, 2014 at 12:26 PM, Erlend Garåsen wrote:
> On 06.02.14 18:18, Karl Wright wrote:
>
>> Actually yes, I found it. Only exceptions/errors are recorded by the solr
>> connector.
>>
>> CONNECTORS-884. However,
[
https://issues.apache.org/jira/browse/CONNECTORS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894032#comment-13894032
]
Karl Wright edited comment on CONNECTORS-883 at 2/7/14 12:38 AM:
---
[
https://issues.apache.org/jira/browse/CONNECTORS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894032#comment-13894032
]
Karl Wright commented on CONNECTORS-883:
Also, r1565501.
> Framework: Job no
[
https://issues.apache.org/jira/browse/CONNECTORS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893937#comment-13893937
]
Karl Wright commented on CONNECTORS-883:
r1565468
> Framework: Job notificat
[
https://issues.apache.org/jira/browse/CONNECTORS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-883.
Resolution: Fixed
> Framework: Job notification thread does not handle notification ser
Ok, we're back then to the question of why your current job run does not
log indexing history for Solr. I'll see if there's any reason that should
be true based on the code.
Karl
On Thu, Feb 6, 2014 at 10:51 AM, Erlend Garåsen wrote:
> On 06.02.14 15:53, Karl Wright wrote:
>
>> Hi Erlend,
>>
>
On 06.02.14 18:18, Karl Wright wrote:
Actually yes, I found it. Only exceptions/errors are recorded by the solr
connector.
CONNECTORS-884. However, I don't think this rises to the level of needing
to respin the RC. Do you agree?
Since we are on RC7 now, I agree. I'll start a complete crawl
[
https://issues.apache.org/jira/browse/CONNECTORS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright resolved CONNECTORS-884.
Resolution: Fixed
r1565362 (trunk)
> Solr connector: Successful index posts are not r
[
https://issues.apache.org/jira/browse/CONNECTORS-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright reassigned CONNECTORS-884:
--
Assignee: Karl Wright
> Solr connector: Successful index posts are not recorded in
Actually yes, I found it. Only exceptions/errors are recorded by the solr
connector.
CONNECTORS-884. However, I don't think this rises to the level of needing
to respin the RC. Do you agree?
Karl
On Thu, Feb 6, 2014 at 12:12 PM, Karl Wright wrote:
> Ok, we're back then to the question of w
Karl Wright created CONNECTORS-884:
--
Summary: Solr connector: Successful index posts are not recorded
in simple history
Key: CONNECTORS-884
URL: https://issues.apache.org/jira/browse/CONNECTORS-884
P
On 06.02.14 15:53, Karl Wright wrote:
Hi Erlend,
Please go into the Simple History, and change the start time of the query
to be one day earlier than the default. By default, Simple History only
reports the last hour's worth of events.
Then it only displays the crawl which completed tonight b
Hi Erlend,
The pgadmin queries you did without startdate times are returning ingest
records. Those that include the startdate do not. Therefore it is the
startdate restriction that is causing you to miss the records.
Karl
On Thu, Feb 6, 2014 at 9:59 AM, Erlend Garåsen wrote:
>
> And why do
Hi Erlend,
Please go into the Simple History, and change the start time of the query
to be one day earlier than the default. By default, Simple History only
reports the last hour's worth of events.
Thanks,
Karl
On Thu, Feb 6, 2014 at 9:50 AM, Erlend Garåsen wrote:
> On 06.02.14 15:25, Karl W
And why do I get the following result from pgAdmin when I run the
following SQL?:
select * from repohistory where entityid =
'http://www.ibsen.uio.no/brevmottakere.xhtml?bokstav=H'
54251;1391440247586;1391440244203;1391440247542;"http://www.ibsen.uio.no/brevmottakere.xhtml?bokstav=H";"Web";"d
On 06.02.14 15:25, Karl Wright wrote:
So I conclude that simple history is working fine, but since it is only
returning indexing results within the last hour by default it is confusing
you. I also think it is likely that documents are getting skipped because
you've crawled this set before with
Hi Erlend,
Your "SELECT * FROM repohistory WHERE owner='Web' AND
starttime>1391691978799 ORDER BY starttime DESC,id DESC LIMIT 21" query is
not returning any document ingest records either. It looks like there has
been no indexing after the start time you specified.
So I conclude that simple his
On 06.02.14 14:46, Karl Wright wrote:
You want to put this in properties.xml:
Thanks.
This is a simplified query, the one which is generated by only selecting
the document ingest activity. No results from pgAdmin:
SELECT id AS id,activitytype AS activity,starttime AS
starttime,(endtime-sta
You want to put this in properties.xml:
Karl
On Thu, Feb 6, 2014 at 8:40 AM, Erlend Garåsen wrote:
>
> Anny suggestion what to include in logging.ini? I have tried the following
> without any success:
> log4j.logger.org.postgresql=DEBUG
> log4j.logger.java.sql.Connection=DEBUG
> log4j.logger
Anny suggestion what to include in logging.ini? I have tried the
following without any success:
log4j.logger.org.postgresql=DEBUG
log4j.logger.java.sql.Connection=DEBUG
log4j.logger.java.sql=DEBUG
log4j.logger.java.sql.ResultSet=TRACE
Erlend
On 06.02.14 13:34, Karl Wright wrote:
Hi Erlend,
Hi Erlend,
This isn't making much sense. Nothing here has changed, AFAIK, between
1.4.1 and 1.5. If you want to see the queries being submitted for the
simple history, try these steps:
(1) Stop agents process and Resin
(2) Enable db debugging
(3) Start Resin
(4) try the simple history in the UI
On 06.02.14 12:41, Erlend Garåsen wrote:
p://www.ibsen.uio.no/diktsamlinger.xhtml]} 0 16
select * from repohistory where entityid like
'%www.ibsen.uio.no/diktsamlinger.xhtml%'
11227;1391439283905;1391439277790;1391439283890;"http://www.ibsen.uio.no/diktsamlinger.xhtml";"Web";"fetch";"200";
1
On 06.02.14 12:07, Karl Wright wrote:
Oh - the other obvious reason for no indexing is that there many be no
changes in the document.
Nope, it's actually posting to Solr, but these activities do not show up
in simple history. Here's the log entries from the Solr server:
[2014-02-06 12:25:00.48
Oh - the other obvious reason for no indexing is that there many be no
changes in the document.
Karl
On Thu, Feb 6, 2014 at 5:50 AM, Karl Wright wrote:
> The document *will* be sent to the output connector if "Decided to ingest"
> is logged, so the problem must be in the solr connector itself
The document *will* be sent to the output connector if "Decided to ingest"
is logged, so the problem must be in the solr connector itself. The
following code on the solr side is executed:
if (Logging.ingest.isDebugEnabled())
Logging.ingest.debug("indexPost(): '" + documentURI + "'");
We're still having problems with this release on our test server. It
runs stable and does not hang anymore, but nothing gets sent to Solr.
Since there was a problem with the SSL certificate in previous RCs,
maybe there is a similar problem related to the Solr Output Connector?
We have configu
[
https://issues.apache.org/jira/browse/CONNECTORS-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893202#comment-13893202
]
Karl Wright commented on CONNECTORS-883:
Currently, the JobNotificationThread
[
https://issues.apache.org/jira/browse/CONNECTORS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893188#comment-13893188
]
Karl Wright edited comment on CONNECTORS-879 at 2/6/14 9:07 AM:
[
https://issues.apache.org/jira/browse/CONNECTORS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893188#comment-13893188
]
Karl Wright commented on CONNECTORS-879:
Yes. Please try it.
> java.lang.N
33 matches
Mail list logo
