[jira] [Commented] (OLINGO-1284) V4: Build 4.5.0 release
[ https://issues.apache.org/jira/browse/OLINGO-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651129#comment-16651129 ] Dave Moten commented on OLINGO-1284: I see the maven artifacts for v4.5.0 were deployed to Maven Central in August but there is no tag on the git repo for that release (and I would like to edit and build the source at that version). Can you fix please? > V4: Build 4.5.0 release > --- > > Key: OLINGO-1284 > URL: https://issues.apache.org/jira/browse/OLINGO-1284 > Project: Olingo > Issue Type: Task > Components: odata4-client, odata4-commons, odata4-ext, odata4-server >Affects Versions: (Java) V4 4.4.0 >Reporter: Christian Amend >Assignee: Christian Amend >Priority: Major > Fix For: (Java) V4 4.5.0 > > > Build the 4.5.0 release > Tasks: > Release Candidate > Upload to storage > Start Voting > Upload to Maven Central > Upload to release store > Update JavaDoc > Send Release Mail to announce mailing list -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON response body
[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Webster updated OLINGO-1302: -- Description: Olingo V4 is slower than Olingo V2 when de-serializing the JSON response body. The following request to the OData V2 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] The following request to the OData V4 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] When parsing the V2 response by calling the EntityProvider.readFeed() method, the elapsed time is approximately 180 ms. When parsing the V4 response by calling the getODataEntitySet() method, the elapsed time is approximately 320 ms. I have attached a zipped up Eclipse project (olingo-performance-test) which contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). These programs can be run to compare the performance of the JSON deserialization in Olingo V2 and V4. The Northwind metadata and the JSON response body are read from files included in the project. I have attached a snapshot image from a SAP Java Profiling tool showing profiling on the TestOlingoV4 program. was: The following request to the OData V2 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] The following request to the OData V4 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] When parsing the V2 response by calling the EntityProvider.readFeed() method, the elapsed time is approximately 180 ms. When parsing the V4 response by calling the getODataEntitySet() method, the elapsed time is approximately 320 ms. I have attached a zipped up Eclipse project (olingo-performance-test) which contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). These programs can be run to compare the performance of the JSON deserialization in Olingo V2 and V4. The Northwind metadata and the JSON response body are read from files included in the project. I have attached a snapshot image from a SAP Java Profiling tool showing profiling on the TestOlingoV4 program. > Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON > response body > -- > > Key: OLINGO-1302 > URL: https://issues.apache.org/jira/browse/OLINGO-1302 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.4.0 >Reporter: Scott Webster >Priority: Critical > Labels: performance > Attachments: TestOlingoV4.Profiling.PNG, olingo-performance-test.zip > > > Olingo V4 is slower than Olingo V2 when de-serializing the JSON response body. > The following request to the OData V2 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > The following request to the OData V4 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > When parsing the V2 response by calling the EntityProvider.readFeed() method, > the elapsed time is approximately 180 ms. > When parsing the V4 response by calling the getODataEntitySet() method, the > elapsed time is approximately 320 ms. > I have attached a zipped up Eclipse project (olingo-performance-test) which > contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). > These programs can be run to compare the performance of the JSON > deserialization in Olingo V2 and V4. > The Northwind metadata and the JSON response body are read from files > included in the project. > I have attached a snapshot image from a SAP Java Profiling tool showing > profiling on the TestOlingoV4 program. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON response body
[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Webster updated OLINGO-1302: -- Summary: Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON response body (was: Performance: Olingo V4 is slower than Olingo V2 when parsing query response body) > Performance: Olingo V4 is slower than Olingo V2 when de-serializing JSON > response body > -- > > Key: OLINGO-1302 > URL: https://issues.apache.org/jira/browse/OLINGO-1302 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.4.0 >Reporter: Scott Webster >Priority: Critical > Labels: performance > Attachments: TestOlingoV4.Profiling.PNG, olingo-performance-test.zip > > > The following request to the OData V2 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > The following request to the OData V4 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > When parsing the V2 response by calling the EntityProvider.readFeed() method, > the elapsed time is approximately 180 ms. > When parsing the V4 response by calling the getODataEntitySet() method, the > elapsed time is approximately 320 ms. > I have attached a zipped up Eclipse project (olingo-performance-test) which > contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). > These programs can be run to compare the performance of the JSON > deserialization in Olingo V2 and V4. > The Northwind metadata and the JSON response body are read from files > included in the project. > I have attached a snapshot image from a SAP Java Profiling tool showing > profiling on the TestOlingoV4 program. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when parsing query response body
[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Webster updated OLINGO-1302: -- Description: The following request to the OData V2 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] The following request to the OData V4 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] When parsing the V2 response by calling the EntityProvider.readFeed() method, the elapsed time is approximately 180 ms. When parsing the V4 response by calling the getODataEntitySet() method, the elapsed time is approximately 320 ms. I have attached a zipped up Eclipse project (olingo-performance-test) which contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). These programs can be run to compare the performance of the JSON deserialization in Olingo V2 and V4. The Northwind metadata and the JSON response body are read from files included in the project. I have attached a snapshot image from a SAP Java Profiling tool showing profiling on the TestOlingoV4 program. was: The following request to the OData V2 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] The following request to the OData V4 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] When parsing the V2 response by calling the EntityProvider.readFeed() method, the elapsed time is approximately 180 ms. When parsing the V4 response by calling the getODataEntitySet() method, the elapsed time is approximately 320 ms. I have attached a zipped up Eclipse project (olingo-performance-test) which contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). These programs can be run to compare the performance of the JSON deserialization in Olingo V2 and V4. The Northwind metadata and the JSON response body are read from files included in the project. > Performance: Olingo V4 is slower than Olingo V2 when parsing query response > body > > > Key: OLINGO-1302 > URL: https://issues.apache.org/jira/browse/OLINGO-1302 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.4.0 >Reporter: Scott Webster >Priority: Critical > Labels: performance > Attachments: TestOlingoV4.Profiling.PNG, olingo-performance-test.zip > > > The following request to the OData V2 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > The following request to the OData V4 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > When parsing the V2 response by calling the EntityProvider.readFeed() method, > the elapsed time is approximately 180 ms. > When parsing the V4 response by calling the getODataEntitySet() method, the > elapsed time is approximately 320 ms. > I have attached a zipped up Eclipse project (olingo-performance-test) which > contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). > These programs can be run to compare the performance of the JSON > deserialization in Olingo V2 and V4. > The Northwind metadata and the JSON response body are read from files > included in the project. > I have attached a snapshot image from a SAP Java Profiling tool showing > profiling on the TestOlingoV4 program. > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when parsing query response body
[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Webster updated OLINGO-1302: -- Attachment: TestOlingoV4.Profiling.PNG > Performance: Olingo V4 is slower than Olingo V2 when parsing query response > body > > > Key: OLINGO-1302 > URL: https://issues.apache.org/jira/browse/OLINGO-1302 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.4.0 >Reporter: Scott Webster >Priority: Critical > Labels: performance > Attachments: TestOlingoV4.Profiling.PNG, olingo-performance-test.zip > > > The following request to the OData V2 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > The following request to the OData V4 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > When parsing the V2 response by calling the EntityProvider.readFeed() method, > the elapsed time is approximately 180 ms. > When parsing the V4 response by calling the getODataEntitySet() method, the > elapsed time is approximately 320 ms. > I have attached a zipped up Eclipse project (olingo-performance-test) which > contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). > These programs can be run to compare the performance of the JSON > deserialization in Olingo V2 and V4. > The Northwind metadata and the JSON response body are read from files > included in the project. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when parsing query response body
[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Webster updated OLINGO-1302: -- Attachment: olingo-performance-test.zip > Performance: Olingo V4 is slower than Olingo V2 when parsing query response > body > > > Key: OLINGO-1302 > URL: https://issues.apache.org/jira/browse/OLINGO-1302 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.4.0 >Reporter: Scott Webster >Priority: Critical > Labels: performance > Attachments: olingo-performance-test.zip > > > The following request to the OData V2 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > The following request to the OData V4 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > When parsing the V2 response by calling the EntityProvider.readFeed() method, > the elapsed time is approximately 180 ms. > When parsing the V4 response by calling the getODataEntitySet() method, the > elapsed time is approximately 320 ms. > I have attached a zipped up Eclipse project (olingo-performance-test) which > contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). > These programs can be run to compare the performance of the JSON > deserialization in Olingo V2 and V4. > The Northwind metadata and the JSON response body are read from files > included in the project. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when parsing query response body
[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Webster updated OLINGO-1302: -- Description: The following request to the OData V2 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] The following request to the OData V4 Microsoft NorthWind source returns 500 records with 26 columns: [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] When parsing the V2 response by calling the EntityProvider.readFeed() method, the elapsed time is approximately 180 ms. When parsing the V4 response by calling the getODataEntitySet() method, the elapsed time is approximately 320 ms. I have attached a zipped up Eclipse project (olingo-performance-test) which contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). These programs can be run to compare the performance of the JSON deserialization in Olingo V2 and V4. The Northwind metadata and the JSON response body are read from files included in the project. was: The following request to the OData V2 Microsoft NorthWind source returns 500 records with 26 columns: http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json The following request to the OData V4 Microsoft NorthWind source returns 500 records with 26 columns: http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json When parsing the V2 response by calling the EntityProvider.readFeed() method, the elapsed time is 44 ms. When parsing the V4 response by calling the getBody() method on ODataRetrieveResponse, the elapsed time is 500 ms. > Performance: Olingo V4 is slower than Olingo V2 when parsing query response > body > > > Key: OLINGO-1302 > URL: https://issues.apache.org/jira/browse/OLINGO-1302 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.4.0 >Reporter: Scott Webster >Priority: Critical > Labels: performance > Attachments: olingo-performance-test.zip > > > The following request to the OData V2 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > The following request to the OData V4 Microsoft NorthWind source returns 500 > records with 26 columns: > > [http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json] > When parsing the V2 response by calling the EntityProvider.readFeed() method, > the elapsed time is approximately 180 ms. > When parsing the V4 response by calling the getODataEntitySet() method, the > elapsed time is approximately 320 ms. > I have attached a zipped up Eclipse project (olingo-performance-test) which > contains two Java programs (TestOlingoV2.java, TestOlingoV4.java). > These programs can be run to compare the performance of the JSON > deserialization in Olingo V2 and V4. > The Northwind metadata and the JSON response body are read from files > included in the project. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1302) Performance: Olingo V4 is slower than Olingo V2 when parsing query response body
[ https://issues.apache.org/jira/browse/OLINGO-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Webster updated OLINGO-1302: -- Summary: Performance: Olingo V4 is slower than Olingo V2 when parsing query response body (was: Performance: Olingo V4 is ten times slower than Olingo V2 when parsing query response body) > Performance: Olingo V4 is slower than Olingo V2 when parsing query response > body > > > Key: OLINGO-1302 > URL: https://issues.apache.org/jira/browse/OLINGO-1302 > Project: Olingo > Issue Type: Bug > Components: odata4-client >Affects Versions: (Java) V4 4.4.0 >Reporter: Scott Webster >Priority: Critical > Labels: performance > > The following request to the OData V2 Microsoft NorthWind source returns 500 > records with 26 columns: > http://services.odata.org/V2/Northwind/Northwind.svc/Invoices?$top=500&$format=json > The following request to the OData V4 Microsoft NorthWind source returns 500 > records with 26 columns: > http://services.odata.org/V4/Northwind/Northwind.svc/Invoices?$top=500&$format=json > When parsing the V2 response by calling the EntityProvider.readFeed() method, > the elapsed time is 44 ms. > When parsing the V4 response by calling the getBody() method on > ODataRetrieveResponse, the elapsed time is 500 ms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OLINGO-1301) In Spring Boot application is impossible to redefine Metadata with mapping model XML
[ https://issues.apache.org/jira/browse/OLINGO-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16650725#comment-16650725 ] Michael Bolz commented on OLINGO-1301: -- Hi [~chebotarev_sa], I take your patch and changed it slightly. See Brach [OLINGO-1301|https://git-wip-us.apache.org/repos/asf?p=olingo-odata2.git;a=shortlog;h=refs/heads/OLINGO-1301]. If this is fine for you I will merge it into the master. Kind Regards, Michael > In Spring Boot application is impossible to redefine Metadata with mapping > model XML > -- > > Key: OLINGO-1301 > URL: https://issues.apache.org/jira/browse/OLINGO-1301 > Project: Olingo > Issue Type: Bug > Components: odata2-jpa >Affects Versions: V2 2.0.10 >Reporter: Sergey Chebotarev >Assignee: Michael Bolz >Priority: Major > Attachments: patch.diff, screen.png > > > In Spring Boot application is impossible to redefine Metadata with mapping > model XML. Application have not access by Mapping model XML form resource > directory. Hard coded prefix ''../../" does not allow access to the file. > See attachment. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OLINGO-1308) Support HTTP HEAD method for entity requests
[ https://issues.apache.org/jira/browse/OLINGO-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike H updated OLINGO-1308: --- Affects Version/s: (Java) V4 4.4.0 > Support HTTP HEAD method for entity requests > > > Key: OLINGO-1308 > URL: https://issues.apache.org/jira/browse/OLINGO-1308 > Project: Olingo > Issue Type: New Feature >Affects Versions: (Java) V4 4.4.0 >Reporter: Mike H >Priority: Minor > > Currently HEAD is only supported for metadata and service documents, can it > be extended to the other GET requests for entities? > This relates to ticket OLINGO-995 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OLINGO-1308) Support HTTP HEAD method for entity requests
Mike H created OLINGO-1308: -- Summary: Support HTTP HEAD method for entity requests Key: OLINGO-1308 URL: https://issues.apache.org/jira/browse/OLINGO-1308 Project: Olingo Issue Type: New Feature Reporter: Mike H Currently HEAD is only supported for metadata and service documents, can it be extended to the other GET requests for entities? This relates to ticket OLINGO-995 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
