| commit | 5c4b7e143fabe2a68f232b73065631f335ccb32b | [log] [tgz] |
|---|---|---|
| author | Kirk Lund <klund@apache.org> | Wed Sep 08 09:30:50 2021 -0700 |
| committer | Kirk Lund <klund@apache.org> | Wed Sep 29 10:30:00 2021 -0700 |
| tree | 6532a444450eadc8e1b34f64105f8d15810cc0e4 | |
| parent | e4aee56d4edc9bc86f5f99c42fc61c4d502cc0b2 [diff] |
GEODE-9486: Fix validate-serializable-objects (#6823) Rename DistributedSystemService to SanctionedSerializablesService and remove unused init(DistributedSystem). Move SanctionedSerializablesService to geode-serialization. Implement SanctionedSerializablesService in both geode-core and geode-management to remove special case for each in InternalDataSerializer. Fix sanctioned serializables support in geode-management and geode-apis-compatible-with-redis. Add sanctioned serializables support to geode-serialization and geode-pulse. Add sanctioned serializables support to geode-junit and geode-dunit to simplify writing tests for validate-serializable-objects and prevent having to list out DUnit Rules and other test framework classes when validate-serializable-objects is enabled. Use ExecutorServiceRule and reformat json strings in RestRegionAPIIntegrationTest. Reorganize QueryCommandDUnitTestBase. Use InvalidClassException instead of Exception in ObjectInputStreamFilterWrapper fatal log message. Improve assertion messages in ResourceUtils. Move loadSanctionedSerializablesServices and loadClassNames to new SanctionedSerializables in geode-serialization. Exclude Pulse GemFireAuthentication from sanctioned serializables. Add SerializationTest Category to all AnalyzeSerializables integration tests. Tidy up SANCTIONED_SERIALIZABLES_DEPENDENCIES_PATTERN. Convert to AssertJ and use BeforeClass in InternalDataSerializerSerializationAcceptlistTest. Note: If Git or GitHub is showing invalid file renames in the diffs, you may need to pull the branch locally and configure diff.renameLimit to something lower than the default value of 50. (cherry picked from commit acbd0ff3c37a5e1fe3018d3f7288df385159ac4c) (cherry picked from commit ba81c3670d85dbb4451030e2c4acb11ca8aef9da) (cherry picked from commit 5b067cae5257e871055acebc94b944d36afb59e9)
Apache Geode is a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures.
Apache Geode pools memory, CPU, network resources, and optionally local disk across multiple processes to manage application objects and behavior. It uses dynamic replication and data partitioning techniques to implement high availability, improved performance, scalability, and fault tolerance. In addition to being a distributed data container, Apache Geode is an in-memory data management system that provides reliable asynchronous event notifications and guaranteed message delivery.
Apache Geode is a mature, robust technology originally developed by GemStone Systems. Commercially available as GemFire™, it was first deployed in the financial sector as the transactional, low-latency data engine used in Wall Street trading platforms. Today Apache Geode technology is used by hundreds of enterprise customers for high-scale business applications that must meet low latency and 24x7 availability requirements.
You can download Apache Geode from the website, run a Docker image, or install with homebrew on OSX. Application developers can load dependencies from Maven Central.
Maven
<dependencies> <dependency> <groupId>org.apache.geode</groupId> <artifactId>geode-core</artifactId> <version>$VERSION</version> </dependency> </dependencies>
Gradle
dependencies { compile "org.apache.geode:geode-core:$VERSION" }
Caches are an abstraction that describe a node in an Apache Geode distributed system.
Within each cache, you define data regions. Data regions are analogous to tables in a relational database and manage data in a distributed fashion as name/value pairs. A replicated region stores identical copies of the data on each cache member of a distributed system. A partitioned region spreads the data among cache members. After the system is configured, client applications can access the distributed data in regions without knowledge of the underlying system architecture. You can define listeners to receive notifications when data has changed, and you can define expiration criteria to delete obsolete data in a region.
Locators provide clients with both discovery and server load balancing services. Clients are configured with locator information, and the locators maintain a dynamic list of member servers. The locators provide clients with connection information to a server.
Apache Geode includes the following features:
See BUILDING.md for instructions on how to build the project.
See TESTING.md for instructions on how to run tests.
Geode requires installation of JDK version 1.8. After installing Apache Geode, start a locator and server:
$ gfsh gfsh> start locator gfsh> start server
Create a region:
gfsh> create region --name=hello --type=REPLICATE
Write a client application (this example uses a Gradle build script):
build.gradle
apply plugin: 'java' apply plugin: 'application' mainClassName = 'HelloWorld' repositories { mavenCentral() } dependencies { compile 'org.apache.geode:geode-core:1.4.0' runtime 'org.slf4j:slf4j-log4j12:1.7.24' }
src/main/java/HelloWorld.java
import java.util.Map; import org.apache.geode.cache.Region; import org.apache.geode.cache.client.*; public class HelloWorld { public static void main(String[] args) throws Exception { ClientCache cache = new ClientCacheFactory() .addPoolLocator("localhost", 10334) .create(); Region<String, String> region = cache .<String, String>createClientRegionFactory(ClientRegionShortcut.CACHING_PROXY) .create("hello"); region.put("1", "Hello"); region.put("2", "World"); for (Map.Entry<String, String> entry : region.entrySet()) { System.out.format("key = %s, value = %s\n", entry.getKey(), entry.getValue()); } cache.close(); } }
Build and run the HelloWorld example:
$ gradle run
The application will connect to the running cluster, create a local cache, put some data in the cache, and print the cached data to the console:
key = 1, value = Hello key = 2, value = World
Finally, shutdown the Geode server and locator:
gfsh> shutdown --include-locators=true
For more information see the Geode Examples repository or the documentation.
Apache Geode applications can be written in these client technologies:
The following libraries are available external to the Apache Geode project:
This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See http://www.wassenaar.org/ for more information.
The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS), has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1, which includes information security software using or performing cryptographic functions with asymmetric algorithms. The form and manner of this Apache Software Foundation distribution makes it eligible for export under the License Exception ENC Technology Software Unrestricted (TSU) exception (see the BIS Export Administration Regulations, Section 740.13) for both object code and source code.
The following provides more details on the included cryptographic software: