kibana create index, POST is not working - kibana

kibana create index is not working.
PUT, GET is working.
POST is not working.
kibana > dev tools > console
PUT a_test_index
GET _cat/indices
yellow open data_audit MnC9Y9yFTJKqLCKGwqq2NQ 5 1 3 0 25.9kb 25.9kb
yellow open .kibana ZCXbosazThOHyKVOIvlJ4A 1 1 2 0 10.7kb 10.7kb
yellow open a_test_index CdPLIvMaTryyYOmdGBBC6A 5 1 0 0 1.1kb 1.1kb
POST a_test_index/doc/1 { "test1": "test2" }
Nothing happened.
browsers developer tools.
f12.
no error.
GET a_test_index/_search
{
"took": 0,
"timed_out": false,
"_shards": {
"total": 5,
"successful": 5,
"skipped": 0,
"failed": 0
},
"hits": {
"total": 0,
"max_score": null,
"hits": []
}
}
kibana > management > index pattern
index pattern: a_test_index
create
Nothing happened. The index was not configured.
browsers developer tools.
f12.
Failed to load resource:
the server responded with a status of 404 (Not Found)
:5601/api/...

Related

Dynamodb stream kinesis - Incomplete hash range found between

I have kinesis stream from DynamoDB. And I am processing it through aws KCL sdk v1.14.0. I see below occasional errors in the logs. I also observe that startingHashKey is always 1 and endingHashKey is 0 for all shards in the dynamodb lease table. Any clue why is this happening?
Incomplete hash range found between {
"leaseKey" : "shardId-00000001601992582645-697387df",
"leaseOwner" : "eu01-stg01-vendor-service-74b4cd66b6-6hcfb:29dafc2f-c87f-4c70-b210-d38db7ebfc87",
"leaseCounter" : 4080,
"concurrencyToken" : null,
"lastCounterIncrementNanos" : null,
"checkpoint" : {
"sequenceNumber" : "47515300000000010794885359",
"subSequenceNumber" : 0,
"shardEnd" : false
},
"pendingCheckpoint" : null,
"ownerSwitchesSinceCheckpoint" : 0,
"parentShardIds" : [ ],
"childShardIds" : [ ],
"hashKeyRange" : {
"startingHashKey" : 0,
"endingHashKey" : 1
}
} and {
"leaseKey" : "shardId-00000001602005637902-6358a08a",
"leaseOwner" : "eu01-stg01-vendor-service-74b4cd66b6-6hcfb:29dafc2f-c87f-4c70-b210-d38db7ebfc87",
"leaseCounter" : 397,
"concurrencyToken" : null,
"lastCounterIncrementNanos" : null,
"checkpoint" : {
"sequenceNumber" : "TRIM_HORIZON",
"subSequenceNumber" : 0,
"shardEnd" : false
},
"pendingCheckpoint" : null,
"ownerSwitchesSinceCheckpoint" : 0,
"parentShardIds" : [ "shardId-00000001601992582736-2c3fc0ff" ],
"childShardIds" : [ ],
"hashKeyRange" : {
"startingHashKey" : 0,
"endingHashKey" : 1
}
}
I also get this error, but the stream seems to work properly. (I am using it to monitor the data change).
Then I dig the source code of this error log, find the part code is added on Jun 22, 2020,
This is the source code: https://github.com/awslabs/amazon-kinesis-client/blob/6fbfc21ad7d6a2722491806a411d168304167f7f/src/main/java/com/amazonaws/services/kinesis/clientlibrary/lib/worker/PeriodicShardSyncManager.java#L298
This is the blame: https://github.com/awslabs/amazon-kinesis-client/blame/6fbfc21ad7d6a2722491806a411d168304167f7f/src/main/java/com/amazonaws/services/kinesis/clientlibrary/lib/worker/PeriodicShardSyncManager.java#L298
This is the commit: https://github.com/awslabs/amazon-kinesis-client/commit/3a88a60a4ee7bb8f969b36cb79e7665a7395b6ec
it is only in the latest version: 1.14.0
So I go back one version to use 1.13.3 then no this error.
I have submitted an issue on the GitHub to see what the reason for the error. https://github.com/awslabs/amazon-kinesis-client/issues/758

Ionic Build Execution failed for task ':app:mergeDebugResources'

FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ':app:mergeDebugResources'.
[string/google_app_id] /home/yushin/Desktop/b/TopStreetZambia/platforms/android/app/src/main/res/values/strings.xml [string/google_app_id] /home/yushin/Desktop/b/TopStreetZambia/platforms/android/app/build/generated/res/google-services/debug/values/values.xml: Error: Duplicate resources
[string/google_api_key] /home/yushin/Desktop/b/TopStreetZambia/platforms/android/app/src/main/res/values/strings.xml [string/google_api_key] /home/yushin/Desktop/b/TopStreetZambia/platforms/android/app/build/generated/res/google-services/debug/values/values.xml: Error: Duplicate resources
it appear they was a duplication in google_app_id and google_app_key they belonged to two files one generated from google services, so what i did was went to android.json file and looked up
"res/values/strings.xml": {
"parents": {
"/resources": [
{
"xml": "<string name=\"google_app_id\">#string/google_app_id</string>",
"count": 1
},
{
"xml": "<string name=\"google_api_key\">#string/google_api_key</string>",
"count": 1
},
....
]
and removed
{
"xml": "<string name=\"google_app_id\">#string/google_app_id</string>",
"count": 1
},
{
"xml": "<string name=\"google_api_key\">#string/google_api_key</string>",
"count": 1
}
that fixed the issue for me.
I solved it by just renaming google_api_key to google_map_api_key
just go to strings.xml and place the cursor at the google_api_key and press shift+f6 to refactor it to the name you want

Why does Tableau Logs [Vertica][ODBC] (11430) Catalog name not supported?

I have been working on Tableau + vertica Solutions.
I have installed relevant vertica ODBC driver from Vertica provided packages .
While going through tdeserver.txt log file, I stumbled upon a line of error log as below :
{
"ts": "2015-12-16T21:42:41.568",
"pid": 51081,
"tid": "23d247",
"sev": "warn",
"req": "-",
"sess": "-",
"site": "{759FD0DA-A1AB-4092-AAD3-36DA0923D151}",
"user": "-",
"k": "database-error",
"v": {
"retcode-desc": "SQL_ERROR",
"retcode": -1,
"protocol": "7fc6730d6000",
"line": 2418,
"file": "/Volumes/build/builds/tableau-9-2/tableau-9-2.15.1201.0018/modules/connectors/tabmixins/main/db/ODBCProtocolImpl.cpp",
"error-records": [{
"error-record": 1,
"error-desc": "[Vertica][ODBC] (11430) Catalog name not supported.",
"sql-state": "HYC00",
"sql-state-desc": "SQLSTATE_API_OPT_FEATURE_NOT_IMPL_ODBC3x",
"native-error": 11430
}]
}
}
This piece of log is repeated several times .
Rest of the setup runs smooth as expected .
Below are the attributes from ~/Library/ODBC/odbc.ini
[ODBC]
Trace = 1
TraceAutoStop = 0
TraceFile = ~/log
TraceLibrary =
ThreePartNaming=1
What am I missing here ?

CSS Visual Regession Testing with BackdropJS - could not run grunt:reference or grunt:test

I tried following this tutorial link on setting up backstop.js
https://joe-watkins.io/css-visual-regression-testing-with-grunt-backstopjs/
I followed all the instructions as required.
But I'm running into this error onscreen.
andy.cmwong#ONLM4800GR8LN32 /c/backstop_test
$ grunt backstop:reference
Running "backstop:reference" (backstop) task
[12:16:30] Using gulpfile c:\backstop_test\bower_components\backstopjs\gulpfile.js
[12:16:30] Starting 'clean'...
bitmaps_reference was cleaned.
[12:16:30] Starting 'bless'...
[12:16:30] Finished 'clean' after 9.82 ms
[12:16:30] Finished 'bless' after 15 ms
[12:16:30] Starting 'reference'...
[12:16:30] Starting 'init'...
[12:16:30] Finished 'init' after 73 μs
[12:16:30] Starting 'test'...
Generating reference files.
[12:16:30] Finished 'test' after 4.03 ms
reference has run.
[12:16:30] Finished 'reference' after 5.24 ms
Testing script failed with code: 1
Looks like an error occured. You may want to try running `$ gulp echo`. This will echo the requested test URL output to the console. You can check this output to verify that the file requested is inde
ed being received in the expected format.
cp: cannot stat `./bitmaps_reference': No such file or directory
ERROR: Error: Command failed: C:\Windows\system32\cmd.exe /s /c "cp -rf ./bitmaps_reference c:\backstop_test\tests"
cp: cannot stat `./bitmaps_reference': No such file or directory
Earlier, there was an additional error which states the gulp.run() is deprecated thus it suggested I need to use another npm module to execute tasks in sequence, which led me to this.
https://www.npmjs.com/package/run-sequence
And I managed to resolved it like so
//under bower_components/gulp/tasks/reference.js
var gulp = require('gulp');
var runSequence = require('run-sequence').use(gulp);
//FIRST CLEAN REFERENCE DIR. THEN TEST
gulp.task('reference', ['clean','bless'], function() {
//gulp.run('test');
runSequence('test');
console.log('reference has run.');
});
It works.
However, I'm still not able to complete the grunt/gulp tasks execution thus I'm really stuck with this.
I'm wondering has anybody tried following the tutorial link above and managed to succeed in getting backstopjs to work?
Your input on this is greatly appreciated.
UPDATE
I forgot to show you what my grunt config setup looks like.
........................
grunt.initConfig({
backstop: {
setup: {
options : {
backstop_path: './bower_components/backstopjs',
test_path: './tests',
setup: false,
configure: true
}
},
test: {
options : {
backstop_path: './bower_components/backstopjs',
test_path: './tests',
create_references: false,
run_tests: true
}
},
reference: {
options : {
backstop_path: '/bower_components/backstopjs',
test_path: './tests',
create_references: true,
run_tests: false
}
}
}
});
......................etc
My backstop.json file
{
"viewports": [
{
"name": "phone",
"width": 320,
"height": 480
},
{
"name": "tablet_v",
"width": 568,
"height": 1024
},
{
"name": "tablet_h",
"width": 1024,
"height": 768
}
],
"scenarios": [
{
"label": "http://getbootstrap.com",
"url": "http://getbootstrap.com",
"hideSelectors": [],
"removeSelectors": [
"#carbonads-container"
],
"selectors": [
"header",
"main",
"body .bs-docs-featurette:nth-of-type(1)",
"body .bs-docs-featurette:nth-of-type(2)",
"footer",
"body"
],
"readyEvent": null,
"delay": 500,
"misMatchThreshold" : 0.1
}
]
}
I managed to get it working last night when I got onto my Linux box(VMWare build), redo the backstopjs setup and successfully perform some test runs.
I did have my original suspicion that it was my Window OS environment that wasn't set up properly so I may have to reinstall npm/node/backstop etc, and have it resolved from there.
All good now.

Why custom element fails to link to interleave whilst linking to filesinks works ok?

I've got my own custom element, lets call it MyElement.
It has request sink pads, and sometimes source pads. When a source pad
is created, MyElement emits a signal which can be intercepted by user. In callback registered with this signal, user can link new source pad with other pad.
The problem is, that MyElement works fine when I try to link its source pads to filesinks directly or via identity elements. However when instead I try to link source pads to the interleave element, pipeline fails.
Similar error happens when I connect MyElement's sources to identity elements with 'dump' property set to true.
What is my element/pipeline missing, that makes pipeline with interleave fail?
identity and filesink have caps type of "any". Do your pads have caps?
Pad Templates:
SINK template: 'sink'
Availability: Always
Capabilities:
ANY
Interleave has the following caps:
Pad Templates:
SINK template: 'sink%d'
Availability: On request
Has request_new_pad() function: gst_interleave_request_new_pad
Capabilities:
audio/x-raw-int
rate: [ 1, 2147483647 ]
channels: 1
endianness: { 1234, 4321 }
width: { 8, 16, 24, 32 }
depth: [ 1, 32 ]
signed: true
audio/x-raw-float
rate: [ 1, 2147483647 ]
channels: 1
endianness: { 1234, 4321 }
width: { 32, 64 }
SRC template: 'src'
Availability: Always
Capabilities:
audio/x-raw-int
rate: [ 1, 2147483647 ]
channels: [ 1, 2147483647 ]
endianness: { 1234, 4321 }
width: { 8, 16, 24, 32 }
depth: [ 1, 32 ]
signed: true
audio/x-raw-float
rate: [ 1, 2147483647 ]
channels: [ 1, 2147483647 ]
endianness: { 1234, 4321 }
width: { 32, 64 }
You may want to read up on the debugging options for GStreamer if you haven't already. A lot can go wrong.
How do I view gstreamer debug output?

Resources