[jira] [Commented] (JENA-1604) Add request hook for HTTP query execution
[ https://issues.apache.org/jira/browse/JENA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16616310#comment-16616310 ] ASF subversion and git services commented on JENA-1604: --- Commit 726f32ca013bf710180669e23c772a5587c98da8 in jena's branch refs/heads/master from ajs6f [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=726f32c ] JENA-1604: fixing indentation > Add request hook for HTTP query execution > - > > Key: JENA-1604 > URL: https://issues.apache.org/jira/browse/JENA-1604 > Project: Apache Jena > Issue Type: Task > Components: Jena >Reporter: Niraj Patel >Assignee: A. Soroka >Priority: Critical > > I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for > updates. I would like to send a custom header that will differ on each > request. Our database, Allegrograph, allows us to pass down custom headers > while querying or updating in order to store that information in access logs. > For each SPARQL request we want to send down unique request markers and > usernames in order to be able to trace from a UI click to backend calls to > queries that were performed in the graph. I did some digging around and it > seems like it's not possible. Using default headers when configuring Apache's > Http Client wouldn't work in this case. The suggestion [~andy.seaborne] made > was to create a request hook in HttpOp where we could add additional headers > as necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1604) Add request hook for HTTP query execution
[ https://issues.apache.org/jira/browse/JENA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16616309#comment-16616309 ] ASF subversion and git services commented on JENA-1604: --- Commit 18a23ca279b3025d4ec12c2977d634c9b86b00f6 in jena's branch refs/heads/master from ajs6f [ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=18a23ca ] JENA-1604: transform HTTP requests > Add request hook for HTTP query execution > - > > Key: JENA-1604 > URL: https://issues.apache.org/jira/browse/JENA-1604 > Project: Apache Jena > Issue Type: Task > Components: Jena >Reporter: Niraj Patel >Assignee: A. Soroka >Priority: Critical > > I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for > updates. I would like to send a custom header that will differ on each > request. Our database, Allegrograph, allows us to pass down custom headers > while querying or updating in order to store that information in access logs. > For each SPARQL request we want to send down unique request markers and > usernames in order to be able to trace from a UI click to backend calls to > queries that were performed in the graph. I did some digging around and it > seems like it's not possible. Using default headers when configuring Apache's > Http Client wouldn't work in this case. The suggestion [~andy.seaborne] made > was to create a request hook in HttpOp where we could add additional headers > as necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1604) Add request hook for HTTP query execution
[ https://issues.apache.org/jira/browse/JENA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16616311#comment-16616311 ] ASF GitHub Bot commented on JENA-1604: -- Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/469 > Add request hook for HTTP query execution > - > > Key: JENA-1604 > URL: https://issues.apache.org/jira/browse/JENA-1604 > Project: Apache Jena > Issue Type: Task > Components: Jena >Reporter: Niraj Patel >Assignee: A. Soroka >Priority: Critical > > I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for > updates. I would like to send a custom header that will differ on each > request. Our database, Allegrograph, allows us to pass down custom headers > while querying or updating in order to store that information in access logs. > For each SPARQL request we want to send down unique request markers and > usernames in order to be able to trace from a UI click to backend calls to > queries that were performed in the graph. I did some digging around and it > seems like it's not possible. Using default headers when configuring Apache's > Http Client wouldn't work in this case. The suggestion [~andy.seaborne] made > was to create a request hook in HttpOp where we could add additional headers > as necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1604) Add request hook for HTTP query execution
[ https://issues.apache.org/jira/browse/JENA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615430#comment-16615430 ] ASF GitHub Bot commented on JENA-1604: -- Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/469 Great, thanks @nirajpatel! I'll wait a couple of days in case anyone has comments, or if another committer approves I'll go ahead and merge. This is a pretty low-impact changeset. > Add request hook for HTTP query execution > - > > Key: JENA-1604 > URL: https://issues.apache.org/jira/browse/JENA-1604 > Project: Apache Jena > Issue Type: Task > Components: Jena >Reporter: Niraj Patel >Assignee: A. Soroka >Priority: Critical > > I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for > updates. I would like to send a custom header that will differ on each > request. Our database, Allegrograph, allows us to pass down custom headers > while querying or updating in order to store that information in access logs. > For each SPARQL request we want to send down unique request markers and > usernames in order to be able to trace from a UI click to backend calls to > queries that were performed in the graph. I did some digging around and it > seems like it's not possible. Using default headers when configuring Apache's > Http Client wouldn't work in this case. The suggestion [~andy.seaborne] made > was to create a request hook in HttpOp where we could add additional headers > as necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1604) Add request hook for HTTP query execution
[ https://issues.apache.org/jira/browse/JENA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615280#comment-16615280 ] Niraj Patel commented on JENA-1604: --- [~ajs6f] thank you for getting to this so quickly! This is perfect. > Add request hook for HTTP query execution > - > > Key: JENA-1604 > URL: https://issues.apache.org/jira/browse/JENA-1604 > Project: Apache Jena > Issue Type: Task > Components: Jena >Reporter: Niraj Patel >Assignee: A. Soroka >Priority: Critical > > I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for > updates. I would like to send a custom header that will differ on each > request. Our database, Allegrograph, allows us to pass down custom headers > while querying or updating in order to store that information in access logs. > For each SPARQL request we want to send down unique request markers and > usernames in order to be able to trace from a UI click to backend calls to > queries that were performed in the graph. I did some digging around and it > seems like it's not possible. Using default headers when configuring Apache's > Http Client wouldn't work in this case. The suggestion [~andy.seaborne] made > was to create a request hook in HttpOp where we could add additional headers > as necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1604) Add request hook for HTTP query execution
[ https://issues.apache.org/jira/browse/JENA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615203#comment-16615203 ] A. Soroka commented on JENA-1604: - [~nirajpatel], can you take a look at the above PR? Would that suit your use case? You would need to define one transformer object that is used on all requests, but it would have full access to each request and could tap into other state or computation as needed. > Add request hook for HTTP query execution > - > > Key: JENA-1604 > URL: https://issues.apache.org/jira/browse/JENA-1604 > Project: Apache Jena > Issue Type: Task > Components: Jena >Reporter: Niraj Patel >Assignee: A. Soroka >Priority: Critical > > I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for > updates. I would like to send a custom header that will differ on each > request. Our database, Allegrograph, allows us to pass down custom headers > while querying or updating in order to store that information in access logs. > For each SPARQL request we want to send down unique request markers and > usernames in order to be able to trace from a UI click to backend calls to > queries that were performed in the graph. I did some digging around and it > seems like it's not possible. Using default headers when configuring Apache's > Http Client wouldn't work in this case. The suggestion [~andy.seaborne] made > was to create a request hook in HttpOp where we could add additional headers > as necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JENA-1604) Add request hook for HTTP query execution
[ https://issues.apache.org/jira/browse/JENA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16615201#comment-16615201 ] ASF GitHub Bot commented on JENA-1604: -- GitHub user ajs6f opened a pull request: https://github.com/apache/jena/pull/469 JENA-1604: transform HTTP requests You can merge this pull request into a Git repository by running: $ git pull https://github.com/ajs6f/jena JENA-1604 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/jena/pull/469.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #469 commit 18a23ca279b3025d4ec12c2977d634c9b86b00f6 Author: ajs6f Date: 2018-09-14T18:25:25Z JENA-1604: transform HTTP requests > Add request hook for HTTP query execution > - > > Key: JENA-1604 > URL: https://issues.apache.org/jira/browse/JENA-1604 > Project: Apache Jena > Issue Type: Task > Components: Jena >Reporter: Niraj Patel >Assignee: A. Soroka >Priority: Critical > > I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for > updates. I would like to send a custom header that will differ on each > request. Our database, Allegrograph, allows us to pass down custom headers > while querying or updating in order to store that information in access logs. > For each SPARQL request we want to send down unique request markers and > usernames in order to be able to trace from a UI click to backend calls to > queries that were performed in the graph. I did some digging around and it > seems like it's not possible. Using default headers when configuring Apache's > Http Client wouldn't work in this case. The suggestion [~andy.seaborne] made > was to create a request hook in HttpOp where we could add additional headers > as necessary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
