Bump orient from 3.2.27 to 3.2.28

[dependabot]

Bumps orient from 3.2.27 to 3.2.28.
Updates com.orientechnologies:orientdb-core from 3.2.27 to 3.2.28

Release notes

Sourced from com.orientechnologies:orientdb-core's releases.

3.2.28

Changes

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

Distributed

• Fixed database sync with enterprise agent

Etl

• Fix concurrent issues in not x86 architectures

Client

• removed duplicate cancel from client code

Artifacts

orientdb-community-3.2.28.tar.gz orientdb-community-3.2.28.zip

orientdb-tp3-3.2.28.tar.gz orientdb-tp3-3.2.28.zip

agent-3.2.28.jar

Changelog

Sourced from com.orientechnologies:orientdb-core's changelog.

       .                                          
      .`        `                                 
      ,      `:.                                  
     `,`    ,:`                                   
     .,.   :,,                                    
     .,,  ,,,                                     
.    .,.:::::  ````                                 :::::::::     :::::::::
,`   .::,,,,::.,,,,,,`;;                      .:    ::::::::::    :::    :::
`,.  ::,,,,,,,:.,,.`  `                       .:    :::      :::  :::     :::
 ,,:,:,,,,,,,,::.   `        `         ``     .:    :::      :::  :::     :::
  ,,:.,,,,,,,,,: `::, ,,   ::,::`   : :,::`  ::::   :::      :::  :::    :::
   ,:,,,,,,,,,,::,:   ,,  :.    :   ::    :   .:    :::      :::  :::::::
    :,,,,,,,,,,:,::   ,,  :      :  :     :   .:    :::      :::  :::::::::

:,,,,,,,,,,:,::, ,, .:::::::: : : .: ::: ::: ::: :::,...,,:,,,,,,,,,: .:,. ,, ,, : : .: ::: ::: ::: ::: .,,,,::,,,,,,,: : , ,, : : : .: ::: ::: ::: ::: ...,::,,,,::.. : .,, :, : : : .: ::::::::::: ::: ::: ,::::,,,. : ,, ::::: : : .: ::::::::: :::::::::: ,,: ,,.
,,, ., MULTI-MODEL ,,. , GRAPH DOCUMENT DATABASE `. COMMUNITY EDITION ` orientdb.com

This document contains the last changes of OrientDB Community Edition.

---

VERSION 3.2.28 - (February, 21 2024)

• Release Notes: https://github.com/orientechnologies/orientdb/wiki/OrientDB-3.2-Release-Notes#3228---21-February-2024

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

... (truncated)

Commits

• 8d803f0 OrientDB prepare release 3.2.28
• e078c09 chore: update history
• 0a5bad9 fix: make sure to use the right node for sync and set online after sync
• c799c90 fix: avoid to fetch database from self node
• dc9a139 test: corrected it test failure after changes in Double Write Log
• 03ae14e chore: update history.txt
• 5b0e984 Dirty counter is updated on write sync.
• 374c88b SYNC flag is removed for DWL channel because we perform sync on data write.
• 4e782e9 We do not need to make fsync during WAL truncation it will be forced by DWL i...
• c50e5d6 DWL is truncated everytime there are tail segments in queue.
• Additional commits viewable in compare view

Updates com.orientechnologies:orientdb-object from 3.2.27 to 3.2.28

Release notes

Sourced from com.orientechnologies:orientdb-object's releases.

3.2.28

Changes

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

Distributed

• Fixed database sync with enterprise agent

Etl

• Fix concurrent issues in not x86 architectures

Client

• removed duplicate cancel from client code

Artifacts

orientdb-community-3.2.28.tar.gz orientdb-community-3.2.28.zip

orientdb-tp3-3.2.28.tar.gz orientdb-tp3-3.2.28.zip

agent-3.2.28.jar

Changelog

Sourced from com.orientechnologies:orientdb-object's changelog.

       .                                          
      .`        `                                 
      ,      `:.                                  
     `,`    ,:`                                   
     .,.   :,,                                    
     .,,  ,,,                                     
.    .,.:::::  ````                                 :::::::::     :::::::::
,`   .::,,,,::.,,,,,,`;;                      .:    ::::::::::    :::    :::
`,.  ::,,,,,,,:.,,.`  `                       .:    :::      :::  :::     :::
 ,,:,:,,,,,,,,::.   `        `         ``     .:    :::      :::  :::     :::
  ,,:.,,,,,,,,,: `::, ,,   ::,::`   : :,::`  ::::   :::      :::  :::    :::
   ,:,,,,,,,,,,::,:   ,,  :.    :   ::    :   .:    :::      :::  :::::::
    :,,,,,,,,,,:,::   ,,  :      :  :     :   .:    :::      :::  :::::::::

:,,,,,,,,,,:,::, ,, .:::::::: : : .: ::: ::: ::: :::,...,,:,,,,,,,,,: .:,. ,, ,, : : .: ::: ::: ::: ::: .,,,,::,,,,,,,: : , ,, : : : .: ::: ::: ::: ::: ...,::,,,,::.. : .,, :, : : : .: ::::::::::: ::: ::: ,::::,,,. : ,, ::::: : : .: ::::::::: :::::::::: ,,: ,,.
,,, ., MULTI-MODEL ,,. , GRAPH DOCUMENT DATABASE `. COMMUNITY EDITION ` orientdb.com

This document contains the last changes of OrientDB Community Edition.

---

VERSION 3.2.28 - (February, 21 2024)

• Release Notes: https://github.com/orientechnologies/orientdb/wiki/OrientDB-3.2-Release-Notes#3228---21-February-2024

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

... (truncated)

Commits

• 8d803f0 OrientDB prepare release 3.2.28
• e078c09 chore: update history
• 0a5bad9 fix: make sure to use the right node for sync and set online after sync
• c799c90 fix: avoid to fetch database from self node
• dc9a139 test: corrected it test failure after changes in Double Write Log
• 03ae14e chore: update history.txt
• 5b0e984 Dirty counter is updated on write sync.
• 374c88b SYNC flag is removed for DWL channel because we perform sync on data write.
• 4e782e9 We do not need to make fsync during WAL truncation it will be forced by DWL i...
• c50e5d6 DWL is truncated everytime there are tail segments in queue.
• Additional commits viewable in compare view

Updates com.orientechnologies:orientdb-graphdb from 3.2.27 to 3.2.28

Release notes

Sourced from com.orientechnologies:orientdb-graphdb's releases.

3.2.28

Changes

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

Distributed

• Fixed database sync with enterprise agent

Etl

• Fix concurrent issues in not x86 architectures

Client

• removed duplicate cancel from client code

Artifacts

orientdb-community-3.2.28.tar.gz orientdb-community-3.2.28.zip

orientdb-tp3-3.2.28.tar.gz orientdb-tp3-3.2.28.zip

agent-3.2.28.jar

Changelog

Sourced from com.orientechnologies:orientdb-graphdb's changelog.

       .                                          
      .`        `                                 
      ,      `:.                                  
     `,`    ,:`                                   
     .,.   :,,                                    
     .,,  ,,,                                     
.    .,.:::::  ````                                 :::::::::     :::::::::
,`   .::,,,,::.,,,,,,`;;                      .:    ::::::::::    :::    :::
`,.  ::,,,,,,,:.,,.`  `                       .:    :::      :::  :::     :::
 ,,:,:,,,,,,,,::.   `        `         ``     .:    :::      :::  :::     :::
  ,,:.,,,,,,,,,: `::, ,,   ::,::`   : :,::`  ::::   :::      :::  :::    :::
   ,:,,,,,,,,,,::,:   ,,  :.    :   ::    :   .:    :::      :::  :::::::
    :,,,,,,,,,,:,::   ,,  :      :  :     :   .:    :::      :::  :::::::::

:,,,,,,,,,,:,::, ,, .:::::::: : : .: ::: ::: ::: :::,...,,:,,,,,,,,,: .:,. ,, ,, : : .: ::: ::: ::: ::: .,,,,::,,,,,,,: : , ,, : : : .: ::: ::: ::: ::: ...,::,,,,::.. : .,, :, : : : .: ::::::::::: ::: ::: ,::::,,,. : ,, ::::: : : .: ::::::::: :::::::::: ,,: ,,.
,,, ., MULTI-MODEL ,,. , GRAPH DOCUMENT DATABASE `. COMMUNITY EDITION ` orientdb.com

This document contains the last changes of OrientDB Community Edition.

---

VERSION 3.2.28 - (February, 21 2024)

• Release Notes: https://github.com/orientechnologies/orientdb/wiki/OrientDB-3.2-Release-Notes#3228---21-February-2024

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

... (truncated)

Commits

• 8d803f0 OrientDB prepare release 3.2.28
• e078c09 chore: update history
• 0a5bad9 fix: make sure to use the right node for sync and set online after sync
• c799c90 fix: avoid to fetch database from self node
• dc9a139 test: corrected it test failure after changes in Double Write Log
• 03ae14e chore: update history.txt
• 5b0e984 Dirty counter is updated on write sync.
• 374c88b SYNC flag is removed for DWL channel because we perform sync on data write.
• 4e782e9 We do not need to make fsync during WAL truncation it will be forced by DWL i...
• c50e5d6 DWL is truncated everytime there are tail segments in queue.
• Additional commits viewable in compare view

Updates com.orientechnologies:orientdb-lucene from 3.2.27 to 3.2.28

Release notes

Sourced from com.orientechnologies:orientdb-lucene's releases.

3.2.28

Changes

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

Distributed

• Fixed database sync with enterprise agent

Etl

• Fix concurrent issues in not x86 architectures

Client

• removed duplicate cancel from client code

Artifacts

orientdb-community-3.2.28.tar.gz orientdb-community-3.2.28.zip

orientdb-tp3-3.2.28.tar.gz orientdb-tp3-3.2.28.zip

agent-3.2.28.jar

Changelog

Sourced from com.orientechnologies:orientdb-lucene's changelog.

       .                                          
      .`        `                                 
      ,      `:.                                  
     `,`    ,:`                                   
     .,.   :,,                                    
     .,,  ,,,                                     
.    .,.:::::  ````                                 :::::::::     :::::::::
,`   .::,,,,::.,,,,,,`;;                      .:    ::::::::::    :::    :::
`,.  ::,,,,,,,:.,,.`  `                       .:    :::      :::  :::     :::
 ,,:,:,,,,,,,,::.   `        `         ``     .:    :::      :::  :::     :::
  ,,:.,,,,,,,,,: `::, ,,   ::,::`   : :,::`  ::::   :::      :::  :::    :::
   ,:,,,,,,,,,,::,:   ,,  :.    :   ::    :   .:    :::      :::  :::::::
    :,,,,,,,,,,:,::   ,,  :      :  :     :   .:    :::      :::  :::::::::

:,,,,,,,,,,:,::, ,, .:::::::: : : .: ::: ::: ::: :::,...,,:,,,,,,,,,: .:,. ,, ,, : : .: ::: ::: ::: ::: .,,,,::,,,,,,,: : , ,, : : : .: ::: ::: ::: ::: ...,::,,,,::.. : .,, :, : : : .: ::::::::::: ::: ::: ,::::,,,. : ,, ::::: : : .: ::::::::: :::::::::: ,,: ,,.
,,, ., MULTI-MODEL ,,. , GRAPH DOCUMENT DATABASE `. COMMUNITY EDITION ` orientdb.com

This document contains the last changes of OrientDB Community Edition.

---

VERSION 3.2.28 - (February, 21 2024)

• Release Notes: https://github.com/orientechnologies/orientdb/wiki/OrientDB-3.2-Release-Notes#3228---21-February-2024

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

... (truncated)

Commits

• 8d803f0 OrientDB prepare release 3.2.28
• e078c09 chore: update history
• 0a5bad9 fix: make sure to use the right node for sync and set online after sync
• c799c90 fix: avoid to fetch database from self node
• dc9a139 test: corrected it test failure after changes in Double Write Log
• 03ae14e chore: update history.txt
• 5b0e984 Dirty counter is updated on write sync.
• 374c88b SYNC flag is removed for DWL channel because we perform sync on data write.
• 4e782e9 We do not need to make fsync during WAL truncation it will be forced by DWL i...
• c50e5d6 DWL is truncated everytime there are tail segments in queue.
• Additional commits viewable in compare view

Updates com.orientechnologies:orientdb-tools from 3.2.27 to 3.2.28

Release notes

Sourced from com.orientechnologies:orientdb-tools's releases.

3.2.28

Changes

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

Distributed

• Fixed database sync with enterprise agent

Etl

• Fix concurrent issues in not x86 architectures

Client

• removed duplicate cancel from client code

Artifacts

orientdb-community-3.2.28.tar.gz orientdb-community-3.2.28.zip

orientdb-tp3-3.2.28.tar.gz orientdb-tp3-3.2.28.zip

agent-3.2.28.jar

Changelog

Sourced from com.orientechnologies:orientdb-tools's changelog.

       .                                          
      .`        `                                 
      ,      `:.                                  
     `,`    ,:`                                   
     .,.   :,,                                    
     .,,  ,,,                                     
.    .,.:::::  ````                                 :::::::::     :::::::::
,`   .::,,,,::.,,,,,,`;;                      .:    ::::::::::    :::    :::
`,.  ::,,,,,,,:.,,.`  `                       .:    :::      :::  :::     :::
 ,,:,:,,,,,,,,::.   `        `         ``     .:    :::      :::  :::     :::
  ,,:.,,,,,,,,,: `::, ,,   ::,::`   : :,::`  ::::   :::      :::  :::    :::
   ,:,,,,,,,,,,::,:   ,,  :.    :   ::    :   .:    :::      :::  :::::::
    :,,,,,,,,,,:,::   ,,  :      :  :     :   .:    :::      :::  :::::::::

:,,,,,,,,,,:,::, ,, .:::::::: : : .: ::: ::: ::: :::,...,,:,,,,,,,,,: .:,. ,, ,, : : .: ::: ::: ::: ::: .,,,,::,,,,,,,: : , ,, : : : .: ::: ::: ::: ::: ...,::,,,,::.. : .,, :, : : : .: ::::::::::: ::: ::: ,::::,,,. : ,, ::::: : : .: ::::::::: :::::::::: ,,: ,,.
,,, ., MULTI-MODEL ,,. , GRAPH DOCUMENT DATABASE `. COMMUNITY EDITION ` orientdb.com

This document contains the last changes of OrientDB Community Edition.

---

VERSION 3.2.28 - (February, 21 2024)

• Release Notes: https://github.com/orientechnologies/orientdb/wiki/OrientDB-3.2-Release-Notes#3228---21-February-2024

Core

• Check if the index exists before checking it's properties
• Make sure to initialize maps on update of value in query engine
• Add name to the OrientDB internal timer
• Removed optimization in query engine that cause failing to update linked records, issue #10077
• Corrected query with content of nested JSON documents to use embedded class
• Add count on the create link result set
• Make sure to call on drop on database drop
• Double Write Log is fsynced on writes. Looks like usage of SYNC flag is not enough
• Double Write Log is not truncated on file flush but only if it reaches file limit
• Double Write Log is truncated every time there are tail segments in queue
• We do not need to make fsync during Write Ahead Log truncation it will be forced by Double Write Log itself
• sync flag is removed for Double Write Log channel because we perform sync on data write
• Dirty counter is updated on write sync

... (truncated)

Commits

• 8d803f0 OrientDB prepare release 3.2.28
• e078c09 chore: update history
• 0a5bad9 fix: make sure to use the right node for sync and set online after sync
• c799c90 fix: avoid to fetch database from self node
• dc9a139 test: corrected it test failure after changes in Double Write Log
• 03ae14e chore: update history.txt
• 5b0e984 Dirty counter is updated on write sync.
• 374c88b SYNC flag is removed for DWL channel because we perform sync on data write.
• 4e782e9 We do not need to make fsync during WAL truncation it will be forced by DWL i...
• c50e5d6 DWL is truncated everytime there are tail segments in queue.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)