Community
Pick of the Week at NebulaGraph - Compiling NebulaGraph with ARM64
Normally the weekly issue covers NebulaGraph Updates and Community Q&As. If something major happens, it will also be covered in the additional Events of the Week section.
The 48th Friday of 2020 is passing soon. Let's see what's new with NebulaGraph.
Events of the week
NebulaGraph Studio v2.0.0-alpha supports querying and exploring data with NebulaGraph v2.0.0 alpha. At the time, data importing and schema indexing is not compatible. We will support these functions in the follow-up releases soon. Please go to the nebula-web-docker v2 directory to try NebulaGraph Studio v2.0.0-alpha.
NebulaGraph Updates
FIND PATHsupports finding the outgoing, incoming, and bi-direct paths. It also supports removing the ring path. Tag:nGQL. PR: https://github.com/vesoft-inc/nebula/pull/2398- Supports compiling NebulaGraph on ARM64. Tag:
Compiling. PR: https://github.com/vesoft-inc/nebula/pull/2392
Community Q&A
This week's topic is from community user @xrfinbj about the relationship between Exchange and Spark Writer.
Question: What is the relationship between Exchange and Spark Writer?
The code for Spark Writer is held in
nebula/src/tools/spark-sstfile-generator. Spark Writer is a distributed data importing tool for NebulaGraph based on Spark. It converts data from various data warehouses into graph data, i.e. vertices and edges, then imports them into graph databases in batches.The code for Exchange is held in
nebula-java/tools/exchange. NebulaGraph Exchange (Exchange for short) is an Apache Spark™ application used to migrate data in a cluster to NebulaGraph in a distributed environment. It supports migrating various batch data and streaming data.For more information, see Import Data to NebulaGraph with Spark.
NebulaGraph: Exchange is migrated from Spark Writer and provides richer data sources based on Spark Writer, such as MySQL, Neo4j, Hive, HBase, Kafka, and Pulsar.
Fixed some problems of Exchange. For example, by default Exchange reads source data from HDFS as strings, which may be different from your graph schema defined in NebulaGraph. Exchange supports automatically matching and converting data types. With it, when a non-string data type is defined in NebulaGraph, Exchange converts the strings into data of the required data type. We will put main efforts on Exchange in the future. If you're using Spark, we suggest you using Exchange to import data.
One thing to add, the TODOs in document means the document is not done but Exchange actually provides the functions. If you're migrating data from other data sources with Exchange, refer to the Neo4j example.
Recommendations for You
Import Data to NebulaGraph with Spark Starting from Spark, the writer shares some practice on indexes, cluster conflict packages.
