This is an automated email from the ASF dual-hosted git repository.
justinchen pushed a change to branch cp-opc-client
in repository https://gitbox.apache.org/repos/asf/iotdb.git
discard 92e528d893c fix
discard c0c8919c7f9 fix
discard 5f69a739877 Pipe: Fixed the OPC UA client connection problem (#17083)
discard c89256db237 spt
discard b6cf835cc29 Optimized the logger when table does not exist in DN
heartbeat && Pipe: Fixed the OPC UA Sink key getter logic and potentail NPE
when closing client && Load: Fixed the missing schema writing for "root" table
(#17063)
discard bde1028e788 fix
discard 1459ded279c Pipe: Implemented OPC Sink for outer server & Set
configuration and changed the default value of the server security policies &
Made the default quality configurable and does not throw when non-value/quality
measurement is encountered (#16944)
add 01dff601a98 Pipe: Implemented OPC Sink for outer server & Set
configuration and changed the default value of the server security policies &
Made the default quality configurable and does not throw when non-value/quality
measurement is encountered (#16944)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (92e528d893c)
\
N -- N -- N refs/heads/cp-opc-client (01dff601a98)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
