type.js | Type.js – Typographic tools for better web type | Frontend Framework library

Both ratings and averageRating should be virtual fields: otherwise, the /0 division is going to crash your schema the moment you have an entry in your collection with product.ratings = 0. So what I would do is, firstly, define ratings by a getter function for a virtual field:

If you notice that when logging rating is equal to {rating: "4"} which is your req.query the value you want is actually req.query.rating so try something like

const rating = req.query.rating

or

const { rating } = req.query

According the comments and more information You have provided, it seems that the issue is the fact that two Flink consumers can't consume from the same partition. So, in Your case only one parallel instance of the operator will consume from kafka partition and the other one will be idle.

In general Flink operator will select MIN([all_downstream_parallel_watermarks]), so In Your case one Kafka Consumer will produce normal Watermarks and the other will never produce anything (flink assumes Long.Min in that case), so Flink will select the lower one which is Long.Min. So, window will never be fired, because while the data is flowing one of the watermarks is never generated. The good practice is to use the same paralellism as the number of Kafka partitions when working with Kafka.

This is the product of a failed git merge, which is the default strategy Git makes when updating your local repository. If you see this, that means there are conflicts in a file, and it will always be a set format:

The line (or lines) between the lines beginning with <<<<<<< and ====== are what you already had in your local copy of the repository (HEAD points to your current branch or commit):

your code does not add new object elements to the response array, but only new references to the same object - so all your values are the same

Assuming that your project builds correctly locally, this kind of issue is 99% related to mismatching versions of Node, so of the build dependencies installed in the end.

Run this command:

The problem is that you are mixing versions of the libraries which do not match and do not work together.

You define the parent as Spring Boot 2.3.5, a version which uses Spring 5.2 but later define the webflux version to 5.3.6. The Spring Data Elasticsearch version 4.1.8 also is built with Spring 5.3.2. I didn't check the recactor and netty versions in detail, but there probably is some conflict as well - it seems that in your pom you defined these dependencies with the versions from Spring Boot 2.4.5 but keep the parent version on 2.3.5.

Your application runs with the following pom (I set the parent to 2.4.5 and removed unneeded explicit dependencies):

Your title input doesn't have a name and your textarea is named body. Add name="title" to input and change textarea name to content

After experimenting I found the answer