Re: Contribution on jena api in Greek
Hello, Thank you very much for your response and interest for our project. I will discuss with Mr Velonis your proposal. In the meantime, I will add the link to our project. Thank you! Euclid Στις Τρί, 19 Φεβ 2019 στις 5:48 μ.μ., ο/η ajs6f έγραψε: > Hello, Euclid, > > First of all, thank you very much for this work! It's really great to see > this interest in Jena, especially in documentation. > > I'm not equipped to render a useful opinion about your work (I don't read > Greek), so I'll leave that to others, but I do want to ask you if you think > you would be able to commit to maintaining this suite of documentation. If > so, we could potentially talk about contributing it to the project, but if > not (which would be very understandable) I think it would be best > maintained as a standalone project. > > As for a link on that page, if you look at the top right, you should see a > button labeled "Improve this Page". You can use the editor available there > to send a change to that page and include your link. I can immediately > commit it. Thanks! > > ajs6f > > > On Feb 14, 2019, at 7:30 AM, Euclid Keramopoulos > wrote: > > > > Hello, > > > > We would like to contribute to Jena Api by developing educational > material > > regarding jena api in Greek. Mr George Velonis, an MSc student, worked > > under my supervision for his final thesis in order to produce that > > educational material. In the http://sw.it.teithe.gr/tutorials/jenagr/ > is > > the greek translation of most of the basic subjects regarding jena api, > > such as RDF API Tutorial, Ontology API, SPARQL Tutorial. > > > > Could you tell me what do you think of the produced material and if it is > > possible to add our Greek tutorial under the “Jena tutorials in other > > languages” section? > > > > Yours sincerely, > > > > Euclid Keramopoulos > > > > -- > > Euclid Keramopoulos > > Associate Professor > > Department of Information Tecnhology > > Alexander Technological Educational Institute of Thessaloniki > > PO Box 141, GR 57400 > > Greece > > Skype: euclidkeramopoulos > > Tel. +302310013998 > > Fax. +302310798256 > > -- Euclid Keramopoulos Associate Professor Department of Information Tecnhology Alexander Technological Educational Institute of Thessaloniki PO Box 141, GR 57400 Greece Skype: euclidkeramopoulos Tel. +302310013998 Fax. +302310798256
[GitHub] ajs6f commented on issue #536: Add support SurroundQueryParser to jena-text
ajs6f commented on issue #536: Add support SurroundQueryParser to jena-text URL: https://github.com/apache/jena/pull/536#issuecomment-467013724 @rvesse I agree, although for the near-term it's worth watching out for [OSGi problems](https://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html) there. As JPMS becomes more widely used and useful, that concern will go away. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
jena/publish
Hi, I’ve committed the several pending changes (Vincent Ventresque and Sorin Gheorghiu) to documentation/query/text-query.html. Is the documentation only published at release points or may it be published now to pick current updates that apply to 3.10? There are pending changes in: spatial, text, fuseki1, dataset_description, fuseji_integration, assembler, migrate_jena2_jena3, and tdb2_cmds. Thank you, Chris
Re: jena/publish
Yes, it's possible to release the site without making a new code release, although I admit I don't know much about it. It's triggered using the Apache CMS system, and can be done using the same controls we use to make commits from the anonymous submissions we get on the website. ajs6f > On Feb 25, 2019, at 9:45 AM, Chris Tomlinson > wrote: > > Hi, > > I’ve committed the several pending changes (Vincent Ventresque and Sorin > Gheorghiu) to documentation/query/text-query.html. > > Is the documentation only published at release points or may it be published > now to pick current updates that apply to 3.10? > > There are pending changes in: spatial, text, fuseki1, dataset_description, > fuseji_integration, assembler, migrate_jena2_jena3, and tdb2_cmds. > > Thank you, > Chris >
CMS diff: Jena Full Text Search
Clone URL (Committers only): https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://jena.apache.org/documentation%2Fquery%2Ftext-query.mdtext Chris Tomlinson Index: trunk/content/documentation/query/text-query.mdtext === --- trunk/content/documentation/query/text-query.mdtext (revision 1854295) +++ trunk/content/documentation/query/text-query.mdtext (working copy) @@ -4,7 +4,7 @@ [Lucene](https://lucene.apache.org) or [ElasticSearch](https://www.elastic.co) (built on Lucene). It gives applications the ability to perform indexed full text -searches within SPARQL queries. Here is a compatibility table: +searches within SPARQL queries. Here is a version compatibility table: | Jena | Lucene | Solr | ElasticSearch | ||---|||
Re: jena/publish
Hi, I just tried to jena/publish via cms after doing an edit and a commit via the cms web i/f and the bookmarklet: svnmucc: E170001: POST of '/repos/infra/!svn/me': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org) I’ve never tried a publish before, and I thought that the creds for the other steps on the cms would be sufficient for the publish step but I guess not. Thanks, Chris > On Feb 25, 2019, at 8:53 AM, ajs6f wrote: > > Yes, it's possible to release the site without making a new code release, > although I admit I don't know much about it. It's triggered using the Apache > CMS system, and can be done using the same controls we use to make commits > from the anonymous submissions we get on the website. > > ajs6f > >> On Feb 25, 2019, at 9:45 AM, Chris Tomlinson >> wrote: >> >> Hi, >> >> I’ve committed the several pending changes (Vincent Ventresque and Sorin >> Gheorghiu) to documentation/query/text-query.html. >> >> Is the documentation only published at release points or may it be published >> now to pick current updates that apply to 3.10? >> >> There are pending changes in: spatial, text, fuseki1, dataset_description, >> fuseji_integration, assembler, migrate_jena2_jena3, and tdb2_cmds. >> >> Thank you, >> Chris >> >
Re: jena/publish
I have always done it by logging into the shell server (minotaur.apache.org) and running publish.pl. I have just that for you so it should be available in a while. If you can svn, you should be able to use the CMS control panel. Andy On 25/02/2019 15:27, Chris Tomlinson wrote: Hi, I just tried to jena/publish via cms after doing an edit and a commit via the cms web i/f and the bookmarklet: svnmucc: E170001: POST of '/repos/infra/!svn/me': authorization failed: Could not authenticate to server: rejected Basic challenge (https://svn.apache.org) I’ve never tried a publish before, and I thought that the creds for the other steps on the cms would be sufficient for the publish step but I guess not. Thanks, Chris On Feb 25, 2019, at 8:53 AM, ajs6f wrote: Yes, it's possible to release the site without making a new code release, although I admit I don't know much about it. It's triggered using the Apache CMS system, and can be done using the same controls we use to make commits from the anonymous submissions we get on the website. ajs6f On Feb 25, 2019, at 9:45 AM, Chris Tomlinson wrote: Hi, I’ve committed the several pending changes (Vincent Ventresque and Sorin Gheorghiu) to documentation/query/text-query.html. Is the documentation only published at release points or may it be published now to pick current updates that apply to 3.10? There are pending changes in: spatial, text, fuseki1, dataset_description, fuseji_integration, assembler, migrate_jena2_jena3, and tdb2_cmds. Thank you, Chris
Re: jena/publish
Thanks. I’ll add your procedure to my note. I was just following the JENA/Release+Process#ReleaseProcess-PublishtheupdatedJenasite for the first time. Is the CMS control panel what is displayed when using the ASF_CMS bookmarklet? If not what is the path to the control panel? Thanks again, Chris > On Feb 25, 2019, at 9:55 AM, Andy Seaborne wrote: > > I have always done it by logging into the shell server (minotaur.apache.org) > and running publish.pl. > > I have just that for you so it should be available in a while. > > If you can svn, you should be able to use the CMS control panel. > >Andy > > On 25/02/2019 15:27, Chris Tomlinson wrote: >> Hi, >> I just tried to jena/publish via cms after doing an edit and a commit via >> the cms web i/f and the bookmarklet: >> svnmucc: E170001: POST of '/repos/infra/!svn/me': authorization failed: >> Could not authenticate to server: rejected Basic challenge >> (https://svn.apache.org) >> I’ve never tried a publish before, and I thought that the creds for the >> other steps on the cms would be sufficient for the publish step but I guess >> not. >> Thanks, >> Chris >>> On Feb 25, 2019, at 8:53 AM, ajs6f wrote: >>> >>> Yes, it's possible to release the site without making a new code release, >>> although I admit I don't know much about it. It's triggered using the >>> Apache CMS system, and can be done using the same controls we use to make >>> commits from the anonymous submissions we get on the website. >>> >>> ajs6f >>> On Feb 25, 2019, at 9:45 AM, Chris Tomlinson wrote: Hi, I’ve committed the several pending changes (Vincent Ventresque and Sorin Gheorghiu) to documentation/query/text-query.html. Is the documentation only published at release points or may it be published now to pick current updates that apply to 3.10? There are pending changes in: spatial, text, fuseki1, dataset_description, fuseji_integration, assembler, migrate_jena2_jena3, and tdb2_cmds. Thank you, Chris >>>
[GitHub] osma commented on issue #536: Add support SurroundQueryParser to jena-text
osma commented on issue #536: Add support SurroundQueryParser to jena-text URL: https://github.com/apache/jena/pull/536#issuecomment-467075475 I think it's a pity this PR merges the two methods into one, making the code a bit messier and more difficult to understand. Is that because SurroundQueryParser doesn't implement the normal QueryParser interface? Other than that, I don't have any objections to this PR, it even comes with unit tests. Docs have to be updated too after the merge. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] DamienFontaine commented on issue #536: Add support SurroundQueryParser to jena-text
DamienFontaine commented on issue #536: Add support SurroundQueryParser to jena-text URL: https://github.com/apache/jena/pull/536#issuecomment-467100377 @osma Yes, the SurroundQueryParser doesn't implement org.apache.lucene.queryparser.classic.QueryParser but all parsers can return a org.apache.lucene.search.Query. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] seaninryan commented on issue #534: [WIP] Proof of concept for prometheus endpoint
seaninryan commented on issue #534: [WIP] Proof of concept for prometheus
endpoint
URL: https://github.com/apache/jena/pull/534#issuecomment-467156265
I changed what I'd done to use micrometer.. the creation of the required
objects is a bit tricky so for now I've just done it in the servlet `init()`
method
I just made it use the `JvmMemoryMetrics` class to pull in some standard
stuff and added a `FusekiRequestsMetrics` class to get those stats that come
from the `DataAccessPointRegistry`
I'd spoken to @Claudenw and looked into having a core dependency on
`micrometer-core` and maybe an `extras` dependency on
`micrometer-registry-prometheus` but I can't see how we'd instantiate the
correct implementation of `MeterRegistry` because the different implementations
all have constructors with different signatures
Anyway you guys might be able to offer some more insight on that... I've
just been looking at spring-boot actuator and trying to see what they've done
there
This is what the metrics look like with what I've set up so far:
```
# HELP jvm_buffer_count_buffers An estimate of the number of buffers in the
pool
# TYPE jvm_buffer_count_buffers gauge
jvm_buffer_count_buffers{id="direct",} 16.0
jvm_buffer_count_buffers{id="mapped",} 51.0
# HELP jvm_memory_committed_bytes The amount of memory in bytes that is
committed for the Java virtual machine to use
# TYPE jvm_memory_committed_bytes gauge
jvm_memory_committed_bytes{area="heap",id="PS Survivor Space",} 4.8758784E7
jvm_memory_committed_bytes{area="heap",id="PS Old Gen",} 2.8311552E8
jvm_memory_committed_bytes{area="heap",id="PS Eden Space",} 9.5944704E7
jvm_memory_committed_bytes{area="nonheap",id="Metaspace",} 3.2899072E7
jvm_memory_committed_bytes{area="nonheap",id="Code Cache",} 1.376256E7
jvm_memory_committed_bytes{area="nonheap",id="Compressed Class Space",}
4063232.0
# HELP jvm_buffer_total_capacity_bytes An estimate of the total capacity of
the buffers in this pool
# TYPE jvm_buffer_total_capacity_bytes gauge
jvm_buffer_total_capacity_bytes{id="direct",} 81543.0
jvm_buffer_total_capacity_bytes{id="mapped",} 4.02663383E8
# HELP fuseki_requests_good
# TYPE fuseki_requests_good gauge
fuseki_requests_good{dataset="/data-set-1",description="Graph Store
Protocol",endpoint="data",operation="GSP_RW",} 154.0
fuseki_requests_good{dataset="/data-set-2",description="File
Upload",endpoint="upload",operation="Upload",} 0.0
fuseki_requests_good{dataset="/data-set-2",description="Graph Store Protocol
(Read)",endpoint="get",operation="GSP_R",} 0.0
fuseki_requests_good{dataset="/data-set-1",description="HTTP
Quads",endpoint="",operation="Quads_RW",} 0.0
fuseki_requests_good{dataset="/data-set-2",description="HTTP
Quads",endpoint="",operation="Quads_RW",} 0.0
fuseki_requests_good{dataset="/data-set-2",description="SPARQL
Query",endpoint="sparql",operation="Query",} 0.0
fuseki_requests_good{dataset="/data-set-1",description="File
Upload",endpoint="upload",operation="Upload",} 0.0
fuseki_requests_good{dataset="/data-set-1",description="SPARQL
Update",endpoint="update",operation="Update",} 2.0
fuseki_requests_good{dataset="/data-set-1",description="Graph Store Protocol
(Read)",endpoint="get",operation="GSP_R",} 0.0
fuseki_requests_good{dataset="/data-set-2",description="Graph Store
Protocol",endpoint="data",operation="GSP_RW",} 0.0
fuseki_requests_good{dataset="/data-set-2",description="SPARQL
Query",endpoint="query",operation="Query",} 0.0
fuseki_requests_good{dataset="/data-set-2",description="SPARQL
Update",endpoint="update",operation="Update",} 0.0
fuseki_requests_good{dataset="/data-set-1",description="SPARQL
Query",endpoint="query",operation="Query",} 178.0
fuseki_requests_good{dataset="/data-set-1",description="SPARQL
Query",endpoint="sparql",operation="Query",} 0.0
# HELP jvm_buffer_memory_used_bytes An estimate of the memory that the Java
virtual machine is using for this buffer pool
# TYPE jvm_buffer_memory_used_bytes gauge
jvm_buffer_memory_used_bytes{id="direct",} 81543.0
jvm_buffer_memory_used_bytes{id="mapped",} 4.02663383E8
# HELP fuseki_requests
# TYPE fuseki_requests gauge
fuseki_requests{dataset="/data-set-1",description="Graph Store
Protocol",endpoint="data",operation="GSP_RW",} 154.0
fuseki_requests{dataset="/data-set-2",description="File
Upload",endpoint="upload",operation="Upload",} 0.0
fuseki_requests{dataset="/data-set-2",description="Graph Store Protocol
(Read)",endpoint="get",operation="GSP_R",} 0.0
fuseki_requests{dataset="/data-set-1",description="HTTP
Quads",endpoint="",operation="Quads_RW",} 0.0
fuseki_requests{dataset="/data-set-2",description="HTTP
Quads",endpoint="",operation="Quads_RW",} 0.0
fuseki_requests{dataset="/data-set-2",description="SPARQL
Query",endpoint="sparql",operation="Query",} 0.0
fuseki_requests{dataset="/data-set
[GitHub] seaninryan commented on a change in pull request #534: [WIP] Proof of concept for prometheus endpoint
seaninryan commented on a change in pull request #534: [WIP] Proof of concept
for prometheus endpoint
URL: https://github.com/apache/jena/pull/534#discussion_r259990280
##
File path:
jena-fuseki2/jena-fuseki-core/src/main/java/org/apache/jena/fuseki/ctl/ActionPrometheus.java
##
@@ -0,0 +1,68 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.jena.fuseki.ctl;
+
+import io.micrometer.core.instrument.binder.jvm.JvmMemoryMetrics;
+import io.micrometer.prometheus.PrometheusConfig;
+import io.micrometer.prometheus.PrometheusMeterRegistry;
+import java.io.IOException;
+import javax.servlet.ServletConfig;
+import javax.servlet.ServletException;
+import javax.servlet.ServletOutputStream;
+import javax.servlet.http.HttpServletRequest;
+import javax.servlet.http.HttpServletResponse;
+import org.apache.jena.fuseki.Fuseki;
+import org.apache.jena.fuseki.metrics.FusekiRequestsMetrics;
+import org.apache.jena.fuseki.server.DataAccessPointRegistry;
+import org.apache.jena.fuseki.servlets.HttpAction;
+import org.apache.jena.fuseki.servlets.ServletOps;
+
+import static org.apache.jena.riot.WebContent.charsetUTF8;
+import static org.apache.jena.riot.WebContent.contentTypeJSON;
+
+public class ActionPrometheus extends ActionCtl {
+
+private PrometheusMeterRegistry meterRegistry;
+
+@Override
+public void init(ServletConfig config) throws ServletException {
+DataAccessPointRegistry dataAccessPointRegistry =
(DataAccessPointRegistry)config.getServletContext().getAttribute(Fuseki.attrNameRegistry)
;
+
+meterRegistry = new PrometheusMeterRegistry(PrometheusConfig.DEFAULT);
+new JvmMemoryMetrics().bindTo( meterRegistry );
+new FusekiRequestsMetrics(dataAccessPointRegistry).bindTo(
meterRegistry );
+}
+
+@Override
+final protected void doGet(HttpServletRequest request, HttpServletResponse
response) {
+doCommon(request, response);
+}
+
+@Override
+protected void perform(HttpAction action) {
+try (ServletOutputStream out = action.response.getOutputStream()) {
+action.response.setContentType( contentTypeJSON );
+action.response.setCharacterEncoding( charsetUTF8 );
+
+out.write( meterRegistry.scrape().getBytes() );
Review comment:
this scrape method is only on the Prometheus implementation of
`MeterRegistry` :confused:
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
