Abstract: Methods and systems are disclosed for managing replication of metadata in a master-slave database environment. While metadata is managed on a master node using database tables with transaction guarantees, metadata copies on the slave node are managed using a lightweight key-value store. In exemplary embodiments, master metadata database tables are mapped to respective key-value structures at one or more slave nodes. The key-value structures have entries pointing to respective metadata objects, which include copies of metadata items stored in the master metadata database tables. The key-value structures can be hierarchically organized under a parent key-value structure. Metadata object versions can be organized as a linked list to facilitate multi-version concurrency control. Methods are disclosed for building the key-value store, for retrieving metadata from the store, for updating the store, for providing multi-version concurrency control, and for pruning obsolete metadata versions. Variants are disclosed.

Abstract: Disclosed is a display module including a transparent display panel and a frame to fix a side of the transparent display panel, wherein the frame has a communication unit to receive data from the outside, a controller to process the received data and to output a drive command corresponding to the processed data and a display drive unit to drive the transparent display panel in response to the drive command from the controller. A display system includes a system body and a display module detachably mounted in the system body.

Abstract: Disclosed herein are system, method, and computer program product embodiments for minimizing table lock duration during lost change resynchronization between a source table and a replica table. An embodiment operates by detecting a restart at a source node or a replica node. A source table at the source node is then locked based on the detection. A database transaction is then created for a lost change resynchronization operation and the source table is unlocked. The database transaction is then compared to another database transaction based on its timestamp. Based on the comparison, either the database transaction for the lost change resynchronization operation or the other database transaction is executed.

Abstract: An in-memory database server hosting a tenant of a multi-tenant software architecture can receive a definition of a custom data field that is unique to an organization having isolated access to the tenant. The custom data field can extend a standard table defined by central metadata stored at a system tenant of the multi-tenant software architecture. Tenant private metadata that includes the definition can be stored in memory accessible only to the tenant. A tenant-dependent table that includes the custom data field can be formed, for example by retrieving central metadata defining the standard table from the system tenant and adding the custom data field using the definition. The tenant-dependent table can be presented for access via a database client at the organization. Related systems, articles of manufacture, and computer-implemented methods are disclosed.

Abstract: A computer implemented method is provided. The method comprises initializing a first database image of a first database system based on a recovery image comprising committed transactions, visible uncommitted transactions, and undo logs associated with the visible uncommitted transactions, undoing the visible uncommitted transactions using the undo logs, generating redo logs from the undo logs, replaying the redo logs to create invisible uncommitted transactions, and after replaying the redo logs, replaying transaction logs received from a second database system. Related apparatus, systems, techniques and articles are also described.

Abstract: Methods and systems are disclosed for managing replication of metadata in a master-slave database environment. While metadata is managed on a master node using database tables with transaction guarantees, metadata copies on the slave node are managed using a lightweight key-value store. In exemplary embodiments, master metadata database tables are mapped to respective key-value structures at one or more slave nodes. The key-value structures have entries pointing to respective metadata objects, which include copies of metadata items stored in the master metadata database tables. The key-value structures can be hierarchically organized under a parent key-value structure. Metadata object versions can be organized as a linked list to facilitate multi-version concurrency control. Methods are disclosed for building the key-value store, for retrieving metadata from the store, for updating the store, for providing multi-version concurrency control, and for pruning obsolete metadata versions. Variants are disclosed.

Abstract: Disclosed is a display module including a transparent display panel and a frame to fix a side of the transparent display panel, wherein the frame has a communication unit to receive data from the outside, a controller to process the received data and to output a drive command corresponding to the processed data and a display drive unit to drive the transparent display panel in response to the drive command from the controller. A display system includes a system body and a display module detachably mounted in the system body.

Abstract: Technologies are described providing adaptive query routing in a replicated database environment. The technologies can be used with a variety of replication protocols. Prepared statements, such as for queries, from a database client can be routed to a source node, or a source node and available replica nodes, when a replica node becomes unavailable. When a replica node becomes available again, a prepared statement can be updated to indicate that the updated prepared statement can be executed at nodes including the replica node that is available again. Prepared statement routing can also be used when a portion of replicated data becomes unavailable at a replica node, but a portion of replicated data remains available.

Abstract: Technologies are described for facilitating transaction processing within a database environment. A commit protocol provides for the atomic commit or rollback of a transaction that includes an operation that modifies a metadata entity of the database system and one or more other operations that modify metadata entities or data records of the database system. Innovations are provided for detecting and resolving deadlocks that may arise during transaction processing. Innovations are also provided for providing versioning of metadata entities, including invalidating metadata entities cached at a slave node during the commit at a master node of a transaction that creates a new version of the metadata entity.

Abstract: An in-memory database server hosting a tenant of a multi-tenant software architecture can receive a definition of a custom data field that is unique to an organization having isolated access to the tenant. The custom data field can extend a standard table defined by central metadata stored at a system tenant of the multi-tenant software architecture. Tenant private metadata that includes the definition can be stored in memory accessible only to the tenant. A tenant-dependent table that includes the custom data field can be formed, for example by retrieving central metadata defining the standard table from the system tenant and adding the custom data field using the definition. The tenant-dependent table can be presented for access via a database client at the organization. Related systems, articles of manufacture, and computer-implemented methods are disclosed.

Abstract: An electronic device and method are disclosed herein. An electronic device includes one or more biometric sensors, a memory configured to store an authentication setting table associated with one or more authentication methods associated with one or more authentication levels, and a processor operatively connected to the memory and the one or more biometric sensors. The processor implements the method, including: receive authentication level information associated with a function executed by the electronic device, select at least one authentication method of the one or more authentication methods matching an authentication level indicated by the received authentication level information, and perform user authentication based on the selected at least one authentication method through the one or more biometric sensors.

Abstract: An electronic apparatus includes a user interface device to set and control a function of an electronic apparatus, including a display unit configured to display screens for option groups of the function, a knob configured to enable a manipulation by a user, a depth sensor unit configured to sense depth of the knob, and a control unit, if the function is selected, configured such that an option group transition of the selected function is performed based on depth information according to the manipulation by the user, and a screen of an option group to which the option group transition is made is displayed.

Abstract: An apparatus including a first speaker configured to output higher-frequency sound from among sound of a channel via at least one slit, and a second speaker configured to output lower-frequency sound from among the sound of the channel via at least one other slit. The at least one slit may have a thickness that is less than a wavelength of sound emitted.

Abstract: An audio system, an audio outputting method, and a speaker apparatus are disclosed. The audio system includes a plurality of speaker modules connected to each other, a detection module configured to detect information of the plurality of speaker modules and user information, and a home control module configured to receive an audio signal, process the received audio signal based on the information of the plurality of speaker modules and the user information, and transmit the processed audio signal to the plurality of speaker modules.

Abstract: Systems and methods for generating a metadata log in a database recovery system include generating, at its primary system, a metadata log for a logging period. A change applied to a metadata object accessible from the primary system is detected, and upon detection, the system identifies a pair of a unique metadata identifier and a metadata type for the changed metadata object and determines a metadata structure of the changed metadata object. A data exchange object for the metadata structure is generated and a data exchange element from the data exchange object is created. The metadata log is updated with log information that includes the data exchange element and the pair, which is associated with the data exchange element. Upon the logging period ending, the metadata log is transmitted to a secondary system of the database recovery system for replaying. Related apparatus, systems, techniques and articles are also described.

Abstract: Systems and methods for generating a platform-independent metadata catalog framework of a database system are disclosed. These include receiving, at the database system, a metadata object, and determining a version of the received metadata object. Responsive to determining that a metadata catalog, which has catalog entries associated with unique versions of metadata objects, does not include a catalog entry associated with the version of the received metadata object, a catalog entry in the metadata catalog is created. The created catalog entry is then associated with the version of the received metadata object. Furthermore, a version number based on the version of the received metadata is generated, which is associated with the created catalog entry. Related apparatus, systems, techniques and articles are also described.

Abstract: A computer implemented method is provided. The method comprises initializing a first database image of a first database system based on a recovery image comprising committed transactions, visible uncommitted transactions, and undo logs associated with the visible uncommitted transactions, undoing the visible uncommitted transactions using the undo logs, generating redo logs from the undo logs, replaying the redo logs to create invisible uncommitted transactions, and after replaying the redo logs, replaying transaction logs received from a second database system. Related apparatus, systems, techniques and articles are also described.

Abstract: A method and an apparatus for performing authentication are provided. The method includes performing, by a first authentication unit in a first electronic device, authentication with respect to a second electronic device that requests authentication through a first communication mode and when the second electronic device is authenticated, transmitting first information used for controlling the first electronic device to the second electronic device through the first communication mode and transferring second information indicating that the second electronic device is authenticated to a second authentication unit in the first electronic device.

Abstract: Technologies are described for performing replication within a database environment. For example, replication of database data can be performed using data manipulation language (DML) statements and logical logs. A database node can execute a DML statement, create a logical log comprising the DML statement, and insert the logical log into a logical log queue. The logical log can be sent to one or more other database nodes for execution of the DML statement stored within the logical log. Logical logs can be grouped for sending to other nodes. Logical logs can be executed on a first node and one or more other nodes within the same transaction boundary. Execution of DML statements can be decoupled from sending, receiving, grouping, and/or processing of logical logs.

Abstract: Technologies are described for performing replication of data within a database environment having a source node and a replica node. The source node executes a database operation on at least one database table stored by the source node. The source node asynchronously sends the database operation to the replica node. A prepare commit request is synchronously sent from the source node to the replica node. The source node receives a synchronous precommit acknowledgement from the replica node. The precommit acknowledgement indicates that the database operation was executed at the replica node. The source node commits a transaction associated with the database operation.