Skip to content
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.

What happened to fullSync? #201

Open
abunsen opened this issue Jul 7, 2020 · 2 comments
Open

What happened to fullSync? #201

abunsen opened this issue Jul 7, 2020 · 2 comments

Comments

@abunsen
Copy link

abunsen commented Jul 7, 2020

I noticed in this graphic:
image

There is a reference to a sync command, but when I run ./vulcanizedb --help I only see the following (on v0.1.2-alpha):

Usage:
  vulcanizedb [command]

Available Commands:
  compose               Composes transformer initializer plugin
  composeAndExecute     Composes, loads, and executes transformer initializer plugin
  contractWatcher       Watches events at the provided contract address using fully synced vDB
  execute               executes a precomposed transformer initializer plugin
  headerSync            Syncs VulcanizeDB with local ethereum node's block headers
  help                  Help about any command
  resync                Resync historical data
  streamEthSubscription This command is used to subscribe to the super node eth stream with the provided filters
  superNode             VulcanizeDB SuperNode
  version               Prints the version of vulcanizeDB

Flags:
      --client-ipcPath string                location of geth.ipc file
      --client-levelDbPath string            location of levelDb chaindata
      --config string                        config file location
      --database-hostname string             database hostname (default "localhost")
      --database-name string                 database name (default "vulcanize_public")
      --database-password string             database password
      --database-port int                    database port (default 5432)
      --database-user string                 database user
      --exporter-name string                 name of exporter plugin (default "exporter")
      --filesystem-storageDiffsPath string   location of storage diffs csv file
  -h, --help                                 help for vulcanizedb
      --log-level string                     Log level (trace, debug, info, warn, error, fatal, panic (default "info")
      --logfile string                       file path for logging
      --storageDiffs-source string           where to get the state diffs: csv or geth (default "csv")

Use "vulcanizedb [command] --help" for more information about a command.

Did you remove this or is it now resync?

@i-norden
Copy link
Collaborator

i-norden commented Jul 8, 2020

Hi @abunsen! Yeah we have removed the fullSync command, and are in the process of breaking this repository up into smaller repositories for the different tools contained within. E.g. contract-watcher, header-sync, and ipfs watchers. fullSync can still be used in a previous version of vulcanizedb, or if there is interest in it I can (at some point) create a separate repo that restores that tool. Part of the rationale with removing the fullSync is that the eth ipfs-watcher fulfills and extends the functionality that fullSync provided, although with more overhead due to also processing state data.

@AFDudley
Copy link
Contributor

AFDudley commented Jul 8, 2020

If you'd like continued support for this feature please reach out to me [email protected].

Thanks.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants