The frame options currently visible in the WebUI are:

• Name
• Cache Type
• Cache Size

We should add the remaining frame options.

Success criteria

The following fields are present in the Cluster Admin frame tables:

• Time Quantum
• Inverse Enabled
• Range Enabled
• Fields

The URL to the pilosa server is hardcoded to localhost:10101. We should make that a field in the WebUI.

TopN results should be presented in a table format

Success criteria

Output div for TopN results contains a table of results, with appropriate labels.

The WebUI help menu doesn't reflect the latest PQL changes, and could use some touching up. Making it sticky would help usability as well.

Success criteria

• Help menu is sticky, not hover-over.
• Help menu reflects latest PQL.
• Includes link to Query Language docs.

There should be a way to browse the schema in the WebUI.

I'm picturing an interface with collapsable/expandable tree elements, with a hierarchy of:

• indexes
• frames
• views/fields

Node info is limited in the Cluster Admin section of the WebUI. With the latest changes in the cluster-resize branch, we now have more capabilities we can take advantage of.

The node list can contain the following attributes for each node:

• Node ID
• Cluster ID
• IP address
• Web port
• Gossip port
• Coordinator
• Buttons:
  • Remove node
  • Set coordinator

We also should have the ability to display the cluster status and appropriately handle errors when attempting requests to locked handlers during a resize operation.

Success criteria

• Node metadata and buttons above are present in WebUI
• Cluster status indicator
• API errors should be detected and displayed properly (including cluster resize status if applicable).

Hi there,

I try to compile console but failed.

1. git clone https://github.com/pilosa/console.git
2. cd console
3. make build

go generate github.com/pilosa/console/pkg/static
go build  github.com/pilosa/console/cmd/pilosa-console
/usr/local/Cellar/go/1.12.5/libexec/src/archive/zip/struct.go:24:2:
/usr/local/Cellar/go/1.12.5/libexec/src/path/example_test.go:1:1: expected 'package', found 'EOF'
/usr/local/Cellar/go/1.12.5/libexec/src/internal/fmtsort/sort.go:12:2:
/usr/local/Cellar/go/1.12.5/libexec/src/reflect/all_test.go:1:1: expected 'package', found 'EOF'
make: *** [build] Error 1

my go info:

GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/knight/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/knight/code/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.12.5/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.12.5/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/5d/8gzdb8y16116hwc66q5m45gr0000gn/T/go-build764893398=/tmp/go-build -gno-record-gcc-switches -fno-common"

The UI must be viewed via http[s]://, not file:// as Chrome disallows ajax requests from file:// origins. Therefore, we must run a simple web server. A Go-based server would work well for this, and could package the entire app into one file (the executable).